[release-4.18] OCPBUGS-59387: Add max-concurrent-reconciles flag to machine actuator

[JoelSpeed]

This enables us to configure concurrent reconciliation of the machines to speed up processing of machines during large scale up events.

This matches a performance improvement we made on Azure previously.

Cherry-pick of #125

[openshift-ci-robot]

@JoelSpeed: This pull request references Jira Issue OCPBUGS-59387, which is invalid:

• expected dependent Jira Issue OCPBUGS-59386 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This enables us to configure concurrent reconciliation of the machines to speed up processing of machines during large scale up events.

This matches a performance improvement we made on Azure previously.

Cherry-pick of #125

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[JoelSpeed]

/label backport-risk-assessed
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JoelSpeed]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[damdo]

/lgtm

[JoelSpeed]

/test okd-scos-images

[openshift-ci]

@JoelSpeed: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[JoelSpeed]

/jira refresh

[openshift-ci-robot]

@JoelSpeed: This pull request references Jira Issue OCPBUGS-59387, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-59386 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59386 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[JoelSpeed]

@mehabhalodiya Would you mind looking at this backport as well for me?

[mehabhalodiya]

/lgtm

[JoelSpeed]

/label qe-approved

[openshift-ci-robot]

@JoelSpeed: This pull request references Jira Issue OCPBUGS-59387, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-59386 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59386 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

This enables us to configure concurrent reconciliation of the machines to speed up processing of machines during large scale up events.

This matches a performance improvement we made on Azure previously.

Cherry-pick of #125

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@JoelSpeed: Jira Issue OCPBUGS-59387: Some pull requests linked via external trackers have merged:

• openshift/machine-api-provider-gcp#126

The following pull requests linked via external trackers have not merged:

• openshift/machine-api-operator#1392 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-59387 has not been moved to the MODIFIED state.

In response to this:

This enables us to configure concurrent reconciliation of the machines to speed up processing of machines during large scale up events.

This matches a performance improvement we made on Azure previously.

Cherry-pick of #125

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-api-provider-gcp
This PR has been included in build ose-machine-api-provider-gcp-container-v4.18.0-202508181234.p0.gb2f858b.assembly.stream.el9.
All builds following this will include this PR.