-
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
🌱 Allow control plane count to be configurable in clusterctl upgrade test. #10584
🌱 Allow control plane count to be configurable in clusterctl upgrade test. #10584
Conversation
cc @sbueringer. Had to create this fix as a follow-up to #10498 |
74dcfd5
to
db89010
Compare
db89010
to
4c6f899
Compare
17eadf7
to
d0c419d
Compare
/test pull-cluster-api-e2e-main |
Thx! /lgtm Feel free to cherry-pick |
LGTM label has been added. Git tree hash: 1a65fb3adbd88ca69acb807f9d1fa3c0cb4d98b5
|
[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 |
Thanks! I'll create manual cherry-picks since these changes are across two PRs. I'll incorporate #10498 into the cherry-picks. |
What this PR does / why we need it:
Currently, the clusterctl upgrade test hard-codes the controlPlaneMachineCount to 1. There are some scenarios, such as CAPZ's managed cluster, that create a cluster without a control plane machine. This PR will add a fix to add support for those scenarios.
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 #
/area testing