✨ Avoid reconciling AWSMachinePools when only the status field has changed#5333
Conversation
|
/test ? |
|
@fiunchinho: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use DetailsIn response to this:
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. |
|
/test pull-cluster-api-provider-aws-e2e |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nrb The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Without this event filter, CRs are being reconciled over and over again while CAPA keeps updating their status field with the error coming from the AWS API.
Special notes for your reviewer:
We do the same thing on the other controllers, but this one was missing.
Checklist:
Release note: