-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 MachinePool: automatically bump apiVersions like in our other controllers #7995
🌱 MachinePool: automatically bump apiVersions like in our other controllers #7995
Conversation
controllers Signed-off-by: Stefan Büringer buringerst@vmware.com
Thanks for addressing this issue! |
LGTM label has been added. Git tree hash: 277f7958dc31e018f4a9afa63783403af31cabce
|
@killianmuldoon Can you please take a look if you have some time? The prod-code change is basically only to add the ref bump, everything else is adjusting the tests accordingly Thank you very much! |
I'll merge given lgtm above. Please let me know if you have further comments. Happy to open a follow-up PR. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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:
Approvers can indicate their approval by writing |
/retest |
Signed-off-by: Stefan Büringer buringerst@vmware.com
What this PR does / why we need it:
Today the MachinePool controller is our only controller that doesn't automatically bump the apiVersions in references.
This PR makes the controller consistent with our other controllers.
Please note, if infra or bootstrap providers (e.g. CABPK) drop api versions (like v1alpha3/v1alpha4) without this change existing MachinePools might break and manual user intervention is required.
Example:
A comment about ref bumps in other controllers:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #6778