fix: Limit parallel builds on operator

[christophd]

Usually the builds get strictly queued because of potential image layering in terms of reusing the integration kits. There are situations though where parallel builds on the operator are possible.

• Avoid many running integration builds
• Monitor all builds started by the operator instance and limit max number of running builds according to given setting
• By default use max running builds limit = 3 for build strategy routine
• By default use max running builds limit = 10 for build strategy pod
• Add max running builds setting to IntegrationPlatform

Release Note

fix: Limit parallel builds on operator

[squakez]

In general I think it's a good feature to have. I just am not sure to understand why the controller variable slips into the Build resource. Also, I think this requires an e2e in order to validate such feature, ie, a build really queues up when the max limit is reached.

[christophd]

@claudio4j @squakez could you please rerun the failed workflows? I assume that the errors are flaky tests and are not related to the changes made in this PR

[christophd]

@squakez YAY, checks are green. I will rebase and resolve the conflicts

[squakez]

@squakez YAY, checks are green. I will rebase and resolve the conflicts

Please, mind my previous comments as well:

I just am not sure to understand why the controller variable slips into the Build resource. Also, I think this requires an e2e in order to validate such feature, ie, a build really queues up when the max limit is reached.

Thanks.

[christophd]

@squakez I finally managed to add an E2E test, could you please trigger the workflow once more? thx

[christophd]

@squakez no idea what is happening with the jobs here.
all green on my fork christophd#92

[squakez]

@squakez no idea what is happening with the jobs here. all green on my fork christophd#92

let's give another spin