Kubernetes
You're viewing a free preview. Sign in free to read every script.
Why this exists The PodDisruptionBudget page earlier in this track showed a kubectl drain genuinely refused because a Deployment's PDB allowed zero disruptions. That page stopped at "scale up manually, then drain" as…
Safe Node Draining: Making Room Before a PodDisruptionBudget Says No
A real maintenance procedure — cordon, scale up any Deployment a tight PodDisruptionBudget would otherwise block, then drain — proven against a genuine "Cannot evict pod as it would violate the pod's disruption budget" failure on a real multi-node cluster, and against the same drain succeeding cleanly once the script's scale-up step runs first.
Sign in free to read this script, along with the rest of the library.
Sign in free