Q: Explain how the Kubernetes scheduler makes a placement decision for a new pod.
The scheduler goes through two phases:
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
The scheduler goes through two phases:
- Does the node have enough CPU and memory?
- Does the node match the pod's
nodeSelector? - Does the pod tolerate the node's taints?
- Are the required volumes available in that zone?
- Does the pod's affinity/anti-affinity rule allow this node?
Remediation & Permanent Safeguards
Phase 1: Filtering (Predicates) Eliminate nodes that can't run the pod: Phase 2: Scoring (Priorities) Rank the remaining nodes: The highest-scoring node wins. If tied, a random one is picked. The scheduler then writes the chosen node name into the pod's spec (nodeName field), and the kubelet on that node picks it up and starts the pod.
- Least requested resources (prefer emptier nodes for better bin-packing).
- Affinity preference scores.
- Topology spread.
- Image locality (prefer nodes that already have the image pulled).
- Does the node have enough CPU and memory?
- Does the node match the pod's nodeSelector?
- Does the pod tolerate the node's taints?
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 Explain Kubernetes scheduler 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 Explain Kubernetes scheduler
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 Explain Kubernetes scheduler 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 Explain Kubernetes scheduler Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.