A Kubernetes node goes NotReady and pods are stuck Terminating. What is happening and what do you do?
What they are really testing: Understanding of the control plane and kubelet relationship, and of why Terminating can hang. This separates people who have operated clusters from people who have only deployed to them.
A real interview question
A Kubernetes node goes NotReady and pods are stuck Terminating. What is happening and what do you do?
What most people say
drag me
“I would force delete the stuck pods so they get rescheduled.”
It clears the symptom and can cause data corruption. Force delete tells the API server to forget the pod without knowing whether the container is still running, so a StatefulSet member can end up running twice, writing to the same volume.
The follow-ups they ask next
Why is force delete specifically dangerous for a StatefulSet?
Its guarantee is at most one pod per ordinal. Force delete lets a replacement start while the original may still be running on the unreachable node, so two pods share an identity and a volume.
How do you make workloads survive this automatically?
Spread replicas across nodes and zones with topology constraints, keep spare capacity or fast autoscaling, set pod disruption budgets, and tune tolerations so eviction timing matches your recovery goals.
What the interviewer is listening for
- Explains why Terminating hangs
- Prioritises rescheduling capacity
- Knows the force-delete hazard
What sinks the answer
- Force deletes as first move
- Cannot say what NotReady means
- No node-level diagnosis
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“NotReady means [the kubelet stopped reporting, so the node may be dead or just unreachable]. Pods hang because [graceful delete waits for a kubelet that cannot answer]. I [confirm pods reschedule and there is capacity], then [diagnose disk, memory, kubelet or network]. Force delete is [risky, since two StatefulSet pods could share a volume].”
Keep going with troubleshooting
Junior
A developer says the build passes locally but fails in CI. How do you debug that?
Junior
A production server is failing writes. Disk is 100% full. Walk me through what you do.
Junior
At midnight everything started failing with TLS errors. What happened and what do you do?
Mid
A pod is in CrashLoopBackOff after a deploy. Walk me through your debugging, command by command.
Mid
The deploy reports success, pods are Running, but users get 502s. Where do you look?
Mid
You get paged: the site is down. You have no other information. What are your first five minutes?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free