Skip to content
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

Address stuck rolling update when subnet CIDR do not have usable addresses #924

Open
elankath opened this issue Jul 3, 2024 · 1 comment
Labels
area/robustness Robustness, reliability, resilience related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority)

Comments

@elankath
Copy link
Contributor

elankath commented Jul 3, 2024

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.

@elankath elankath added the kind/enhancement Enhancement, improvement, extension label Jul 3, 2024
@gardener-robot gardener-robot added area/robustness Robustness, reliability, resilience related priority/3 Priority (lower number equals higher priority) labels Jul 3, 2024
@gardener-robot
Copy link

@elankath You have mentioned internal references in the public. Please check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/robustness Robustness, reliability, resilience related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

2 participants