Brian Grant

Why is #kubernetes PodDisruptionBudget a separate object when Rollout Strategy is inlined into Deployment? You need both to be HA.

We can chat about this sometime. Use cases are different: disrupting yourself vs being disrupted. I would like minReadySeconds to be on Pod, though

I get that the consumers are different, but the producer of this info is always the workload operator, IME. So it makes for worse UX having to configure in two places.

One issue is that, like Service, PDB sometimes/often needs to span multiple controller instances. Also, it wouldn't reduce the object count by much. And there hasn't been much demand. Is it otherwise working well for you?

PDB works ok when you define it. There’s just too many things for K8s tenants need to know about to stay highly available. I wrote an internal article, but I should make it a blog. It’s like 10 things to configure.

I’ve been really tempted to do this, TBH. Good to see some prior art. The gotcha was that when I went looking for simplifying abstractions I came up with like 20 different options ranging from FaaS to aPaaS, none of them simple. Google alone contributes to 2 or 3 of them.