Q: A StatefulSet pod can't start because it's trying to attach a volume that's still attached to a terminated pod on a dead node. How do you fix it?
This is a common scenario when a node dies without gracefully releasing its volumes. The PV shows Terminating or the pod shows volume attach error.
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In one of our high-traffic production clusters, our SRE team handled this incident using a standardized runbook. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
This is a common scenario when a node dies without gracefully releasing its volumes. The PV shows Terminating or the pod shows volume attach error.
- Force delete the stuck pod:
kubectl delete pod--grace-period=0 --force - Check if the PV is stuck:
kubectl describe pv— look for the node it's attached to. - On AWS (EBS): use AWS CLI to force detach the volume:
aws ec2 detach-volume --volume-id--force
Remediation & Permanent Safeguards
Steps:
- Check the VolumeAttachment object:
kubectl get volumeattachment— delete the stuck one. - The new pod should then attach the volume successfully.
- Force delete the stuck pod: kubectl delete pod --grace-period=0 --force
- Check if the PV is stuck: kubectl describe pv — look for the node it's attached to.
- On AWS (EBS): use AWS CLI to force detach the volume: aws ec2 detach-volume --volume-id --force
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring StatefulSet start trying Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring StatefulSet start trying
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring StatefulSet start trying Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring StatefulSet start trying Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.