Q: How would you ensure a critical pod always runs on the same node?
Two approaches:
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: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. 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
Two approaches:
- NodeSelector — add a label to the node (
kubectl label node) and addtype=critical nodeSelector: {type: critical}to the pod spec. Simple but inflexible. - Node Affinity — more expressive, supports
requiredDuringSchedulingIgnoredDuringExecution(hard rule) orpreferredDuringScheduling...(soft preference).
Remediation & Permanent Safeguards
For "always the same node" — use requiredDuringSchedulingIgnoredDuringExecution with nodeAffinity. But be careful: if that node goes down, the pod won't reschedule elsewhere.
- NodeSelector — add a label to the node (kubectl label node type=critical) and add nodeSelector: ...
- Node Affinity — more expressive, supports requiredDuringSchedulingIgnoredDuringExecution (hard ru...
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 ensure critical always 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 ensure critical always
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 ensure critical always 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 ensure critical always Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.