Q: Your deployment rollout is stuck. Pods from the new version aren't coming up but old ones are still running. What's happening?
This is typical RollingUpdate behavior when new pods fail healthchecks.
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: "Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. The interviewer is testing: RollingUpdate strategy and rollout debugging.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
This is typical RollingUpdate behavior when new pods fail healthchecks.
- Liveness or readiness probe failing in the new version.
- New image has a bug and is crashing.
- Resource limits hit — new pods can't schedule.
Remediation & Permanent Safeguards
Check: kubectl rollout status deployment/ — it will show if it's stuck. Then kubectl describe pod to see why new pods aren't ready. Common causes: To rollback immediately: kubectl rollout undo deployment/ To investigate without rolling back, describe the new failing pods and check logs.
- Liveness or readiness probe failing in the new version.
- New image has a bug and is crashing.
- Resource limits hit — new pods can't schedule.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Attempting multi-minor Kubernetes version jumps directly during cluster upgrades when configuring deployment rollout stuck Kubernetes explicitly does not support multi-minor version jumps; control plane and worker components require sequential hops to validate API deprecations.
- Upgrading kube-apiserver while leaving critical cluster add-ons and CNI plugins desynchronized when configuring deployment rollout stuck Upgrading kube-apiserver without synchronizing CNI daemonsets or CoreDNS manifests causes silent pod networking failure and DNS timeouts immediately post-upgrade.
- Replacing worker node pools simultaneously rather than adopting sequential rolling node group updates when configuring deployment rollout stuck In-place or simultaneous node pool replacements risk cluster-wide capacity starvation if new AMIs or kubelet versions encounter bootstrapping errors.
- Overlooking terminationGracePeriodSeconds when evicting stateful database or queue consumer pods when configuring deployment rollout stuck Prematurely terminating stateful pods before in-flight transactions commit causes data corruption and unclean lock releases.