← Problem Library
K8s L4 K8S 1344 · 14 min

A StatefulSet pod comes up and fails readiness

Storage is attached correctly, yet startup gates fail because one bootstrap artifact still assumes the previous identity layout.

K8sPlatform ReliabilityLevel 4Pro14 min
Scenario

A StatefulSet recovers onto new infrastructure and later only one member fails readiness with a bootstrap or identity mismatch.

What to check first
  • Identify the primary failure signal in the The Data Moved Correctly and One Bootstrap File Still Belonged to the Old Identity 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 persistent bootstrap artifacts with the current ordinal and hostname assumptions before recreating the PVC.

Questions worth viewing together
What should you verify first when A StatefulSet pod comes up and fails readiness appears?

Community-field Kubernetes problem inspired by StatefulSet recovery discussions where init containers still relied on an old ordinal-specific bootstrap... Stateful recovery can fail on identity artifacts even when the raw data volume is fine.

What usually causes A StatefulSet pod comes up and fails readiness in production?

Teams often blame the storage class when the init logic is still reading an old identity marker.

What should you document after resolving A StatefulSet pod comes up and fails readiness?

Stateful bootstrap logic should be reviewed for ordinal and hostname persistence assumptions during recovery.