← Problem Library
K8s L5 K8S 1234 · 19 min

PodDisruptionBudget blocks node maintenance because one deployment replica is permanently not Ready under the current startup budget

Drain operations appear stuck because the disruption budget depends on readiness math that the workload never actually satisfies in steady state.

K8sPlatform ReliabilityLevel 5Pro19 min
Scenario

A cluster maintenance window starts and node drain cannot proceed because one replica has not been counted as available for a long time.

What to check first
  • Identify the primary failure signal in the PDB Ready Math Trap scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Compare the disruption budget with the real readiness steady state rather than only the replica count.

Questions worth viewing together
What should you verify first when PodDisruptionBudget blocks node maintenance appears?

Community-field Kubernetes operations problem inspired by Reddit and forum threads where PDBs blocked maintenance because one replica never truly became... PDBs protect available replicas, not desired replicas on paper.

What usually causes PodDisruptionBudget blocks node maintenance in production?

Teams often blame drain tooling when the workload has been violating its own availability assumptions all along.

What should you document after resolving PodDisruptionBudget blocks node maintenance?

A single chronically unready replica can make otherwise reasonable PDBs impossible to honor.