ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Pod Disruption Budgets protect your Kubernetes workloads during voluntary maintenance like node drains and autoscaler scale-in, with a concrete three-replica example and the deadlock trade-off to avoid.
Use minAvailable or maxUnavailable to protect replicated workloads during node drains and cluster maintenance.
Learn how a PodDisruptionBudget keeps a minimum number of your application’s pods running while you drain or upgrade nodes, and see the trade‑offs of setting it too tightly.
Learn how a Pod Disruption Budget (PDB) guarantees a minimum number of replicas stay up while you drain nodes, plus a concrete example and the trade‑offs to watch for.
How Pod Disruption Budgets protect workloads during node drains, with configuration steps, version notes, and verification commands.
When draining a node, the Kubernetes control plane evicts pods to honor Pod Disruption Budgets (PDBs). The goal is to verify whether the eviction sequence across multiple overlapping PDBs is deterministic enough to never temporarily violate a PDB’s minimum‑available count. Current documentation notes that the kube‑controller‑manager may evict pods from diffe
kubernetes