Q: Your deployment has 10 replicas. You need to do a zero-downtime deploy of a new version. How do you configure and verify it?
Configure RollingUpdate strategy:
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. 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
Configure RollingUpdate strategy:
kubectl rollout status deployment/— watch it progress.- Monitor your health endpoint / app metrics during rollout.
- If something goes wrong:
kubectl rollout undo deployment/.
Remediation & Permanent Safeguards
maxUnavailable: 0 ensures old pods aren't removed until new ones pass readiness probes. Verify: Also make sure your readiness probe is accurate — this is the gating mechanism for zero-downtime. A bad probe that returns ready too early defeats the whole strategy.
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 2 # max extra pods during update
maxUnavailable: 0 # never kill old pod before new one is ready
- kubectl rollout status deployment/ — watch it progress.
- Monitor your health endpoint / app metrics during rollout.
- If something goes wrong: kubectl rollout undo deployment/.
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 replicas need 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 replicas need 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 replicas need 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 replicas need Prematurely terminating stateful pods before in-flight transactions commit causes data corruption and unclean lock releases.