-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🐛 Fix rollout with unavailable machines #13020
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
🐛 Fix rollout with unavailable machines #13020
Conversation
|
/test pull-cluster-api-e2e-main-gke |
internal/controllers/machinedeployment/machinedeployment_rollout_rollingupdate_test.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_rollout_rollingupdate_test.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_rollout_rollingupdate_test.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_rollout_rollingupdate_test.go
Outdated
Show resolved
Hide resolved
|
/test pull-cluster-api-e2e-main-gke |
|
/retest |
cbe5736 to
3dd9a10
Compare
|
/lgtm |
|
LGTM label has been added. Git tree hash: 4c25fd01ebb92a1a17a28397c31f67ac359608d4
|
|
[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 |
What this PR does / why we need it:
This PR fixes how rollout planners handles case when a rollout starts and all the machines are unavailable (or there are already many available machines).
The fix ensure the system slows down and eventually stops a rollout if the machine deployments is transitioning to a broken state (new MS has unavailable replicas)
/area machinedeployment