Q: A pod is being scheduled and then immediately evicted. What's happening?
Node is under resource pressure. kubelet evicts lower-priority pods to free resources. Check: kubectl describe pod <n> — reason will say ...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
Node is under resource pressure. kubelet evicts lower-priority pods to free resources. Check: kubectl describe pod — reason will say Evicted with a reason (memory, disk). Check node conditions: kubectl describe node — MemoryPressure, DiskPressure, PIDPressure. Fix: increase node size, add more nodes, reduce pod resource requests, clean up eviction-causing pressure (disk full, memory leak).
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Node is under resource pressure. kubelet evicts lower-priority pods to free resources. Check: kubectl describe pod — reason will ."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Node is under resource pressure. kubelet evicts lower-priority pods to free resources. Check: k
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement