Brian Grant

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.

It would be nice to be able to define a default PDB tho. I’m not exactly sure of the default behavior but I often have new tenants forget PDB and then have outages during the first node pool upgrade.

I vaguely recall a proposal for that. I'll look/inquire. In the meantime, the main focus is GA/stable: https://github.com/kubernetes/enhancements/blob/6f42c8560c2c36fde3730fcb0d882b2451cdc00d/keps/sig-apps/20190318-PodDisruptionBudget-graduation-to-stable.md …

There’s a gotcha there by @davidopp, using principle of least surprise to rationalize not surprising the expert that knows PDBs exist and how they work. Better to avoid surprising the non-expert who doesn’t know Kubernetes well. There are vastly more of them.

Wow that issue is ancient... doesn’t look like it’d be easy to get it moving again without convincing the core dissenters.

I just learned there's actually a more recent thread. I'm tracking it down.