Hacker News new | ask | show | jobs
by shizcakes 985 days ago
We've been stuck in this state for all 9 days. We've filed tickets, etc, but no resolution has come about yet. Just re-tried yesterday, still not able to update nodepool.
2 comments

The incident dashboard does mention creating a new node pool with the new version instead of upgrading - as a workaround. Curious to know why this was not an option for you.
If there are stateful workloads.
Even if there are stateful workloads, one has to be prepared to migrate at some point. Nodes can crash, become unreachable, etc. - workloads have to be able to survive such events.

Edit: But I see your point - if their stateful workloads are not "migration/K8S-incident" ready, it's hard to suddenly build that overnight.

Is it a big deal to just build a new cluster and cut traffic over to it via lb or dns?