Address stuck rolling update when subnet CIDR do not have usable addresses #924
Labels
area/robustness
Robustness, reliability, resilience related
kind/enhancement
Enhancement, improvement, extension
priority/3
Priority (lower number equals higher priority)
How to categorize this issue?
/area robustness
/priority 3
What would you like to be added:
Rolling update can get stuck when the available subnet CIDR's don't have sufficient usable addresses for launching machines. See canary issue 5348. We should aim to avoid or mitigate this situation
Why is this needed:
Prevent necessity of manual operator intervention. Let the customer fix their shoot cluster.
The text was updated successfully, but these errors were encountered: