← Problem Library
K8s L6 K8S 1385 · 15 min

A StatefulSet with local PVs keeps one pod Pending

Storage exists, yet the pod cannot bind because the PV and node now speak different zone vocabularies after infrastructure normalization.

K8sPlatform ReliabilityLevel 6Pro15 min
Scenario

A cluster labeling cleanup follows a node replacement and later one StatefulSet pod remains Pending despite free local storage.

What to check first
  • Identify the primary failure signal in the The Volume Was There and Its Geography Was Written in a Dead Dialect 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

Inspect PV node affinity text before replacing nodes or forcing new claims.

Questions worth viewing together
What should you verify first when A StatefulSet with local PVs keeps one pod Pending appears?

Community-field Kubernetes problem inspired by operations and community patterns where a local PV kept an old zone label and blocked scheduling. Storage binding failures often come from stale locality metadata surviving longer than the node that created it.

What usually causes A StatefulSet with local PVs keeps one pod Pending in production?

Teams often blame local PV corruption when the real problem is a stale zone label on the PV affinity.

What should you document after resolving A StatefulSet with local PVs keeps one pod Pending?

Local PV migrations should include a review of node affinity label vocabulary after zone normalization.