← Problem Library
K8s L7 K8S 013 · 25 min

Node draining takes longer than expected because of a PodDisruptionBudget

Covers a situation where the safety gate is correct but an overly strict PDB policy stalls an operational task.

K8sIncident LeadershipLevel 7Team25 min
Scenario

A scenario that narrows down the root cause, centered on designing the balance between high availability and operational convenience, in the situation of node draining taking longer than expected because of a PodDisruptionBudget.

What to check first
  • Identify the primary failure signal in the Availability Policy 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

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.