PodDisruptionBudget is now documented: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ … and https://kubernetes.io/docs/tasks/run-application/configure-pdb/ …. Try it out and give us feedback on how well it works for you. We're looking to advance it from beta to GA:https://github.com/kubernetes/enhancements/issues/85 …
-
Show this thread
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @dave_universetf
Presumably if N+2, that's intended for one planned and one unplanned disruption. PodDisruptionBudget can only moderate planned disruptions. Making maxUnavailable=1 should ensure one planned disruption at a time.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @dave_universetf
Right. We have that issue in Colossus. I assume your storage system is on bare metal, that you don't have network-attached storage, and that you want to allow more than one node to be upgraded at a time?
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
Sounds like a good topic for SIG Apps (engagement info is here: https://github.com/kubernetes/community/tree/master/sig-apps …). Features for stateful and durable workloads are still under design and development.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.