← Problem Library
K8s L4 K8S 1322 · 14 min

A StatefulSet pod stays Pending after force deletion because the old VolumeAttachment object outlives the node and keeps the replacement attach blocked

The dead pod is gone, yet the replacement never mounts because attachment state from the prior node still claims the volume.

K8sPlatform ReliabilityLevel 4Pro14 min
Scenario

An operator force deletes a stuck StatefulSet pod during an incident and later the replacement remains Pending with attach-related events.

What to check first
  • Identify the primary failure signal in the The Pod Disappeared but the Attachment Lock Did Not 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 orphaned attachment objects and controller state before deleting PVCs or storage classes.

Questions worth viewing together
What should you verify first when A StatefulSet pod stays Pending appears?

Community-field Kubernetes problem inspired by community storage incidents where stale VolumeAttachment objects blocked replacement pods. Volume lifecycle state can outlive the pod that originally held it.

What usually causes A StatefulSet pod stays Pending in production?

Teams often blame the new node when a stale attachment object is still pinning the old state.

What should you document after resolving A StatefulSet pod stays Pending?

Force deletion is not the end of the storage story for StatefulSets.