⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Kubernetes Interview Questions Scenario 20 of 207 in Kubernetes
Staff SRE / Principal Architect [L3] Kubernetes Troubleshooting & Debugging Staff SRE Scenario [L3]
🎯 Target Role / Context: Kubernetes Scenario #6 (L3) · Troubleshooting & Debugging

Q: A node in your cluster shows `NotReady`. Your team is panicking because several services are on it. What's your action plan?

Don't panic — check if pods already rescheduled. Kubernetes evicts pods from NotReady nodes after pod-eviction-timeout (default 5 min). Check kubectl get pods -A -o wide | grep .

#Kubernetes #Troubleshooting & Debugging #L3 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. The interviewer is testing: Incident response, node troubleshooting, pod eviction understanding.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

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. The interviewer is testing: Incident response, node troubleshooting, pod eviction understanding.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

  • Don't panic — check if pods already rescheduled. Kubernetes evicts pods from NotReady nodes after pod-eviction-timeout (default 5 min). Check kubectl get pods -A -o wide | grep .
  • Cordon the node — kubectl cordon prevents new pods from scheduling there while you investigate.
  • SSH into the node and check:
  • systemctl status kubelet — is kubelet running?
  • journalctl -u kubelet -n 100 — kubelet logs.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Disk space: df -h. Full disk is a common cause.
  • Memory: free -m.
  • Check the node's conditions: kubectl describe node — look for MemoryPressure, DiskPressure, PIDPressure.
  • If unrecoverable, drain and delete: kubectl drain --ignore-daemonsets --delete-emptydir-data then terminate the VM.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Don't panic — check if pods already rescheduled. Kubernetes evicts pods from NotReady nodes after pod-eviction-timeout (default 5 ."
⚡ 60-Second Elevator Pitch Talking Points
  • Don't panic — check if pods already rescheduled. Kubernetes evicts pods from NotReady nodes after...
  • Cordon the node — kubectl cordon prevents new pods from scheduling there while you investigate.
  • SSH into the node and check:
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Configuring Service selector labels that mismatch underlying Pod manifest metadata when configuring node cluster shows A typo in spec.selector causes the Service endpoints list (kubectl get endpoints) to remain empty, resulting in 503 Service Unavailable or timeouts.
  2. Omitting explicit ingressClassName specifications when running multiple ingress controllers when configuring node cluster shows Without an explicit ingressClassName, ingress resources are either ignored or picked up unpredictably by competing controllers.
  3. Depleting worker node subnet IP address allocations under VPC CNI or Azure CNI when configuring node cluster shows Direct VPC pod networking allocates real subnet IPs; failing to monitor IP pools causes new pods to stay stuck indefinitely in ContainerCreating.
  4. Attempting network triage without inspecting kubectl describe service and EndpointSlice resources when configuring node cluster shows Verifying EndpointSlice population immediately determines whether a connectivity failure is caused by pod labeling, readiness probes, or routing.
Advertisement
📥 FREE DOWNLOAD · 101-PAGE COMPANION HANDBOOK
Studying for Kubernetes & SRE Technical Rounds?
Download the complete 100-question PDF field guide covering all 11 core modules with offline diagnostic runbooks.
📥 Download PDF (Free) Read Online Guide →
Want more Kubernetes scenarios?
Explore our complete collection of scenario-based Kubernetes interview runbooks.
Browse All Kubernetes Questions →