⚡ ~/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 73 of 207 in Kubernetes
Staff SRE / Principal Architect [L3] Kubernetes Advanced Scenarios Staff SRE Scenario [L3]
🎯 Target Role / Context: Kubernetes Scenario #62 (L3) · Advanced Scenarios

Q: A cluster-autoscaler is not scaling up even though pods are Pending. What could be wrong?

Pod is unschedulable for a reason other than resources — e.g., node affinity requires a specific label that no node type has. CA won't add nodes it can't schedule the pod on.

#Kubernetes #Advanced Scenarios #L3 #Container Orchestration #K8s #EC2
🎙️ 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
⚡ 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. 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."

1️⃣

Initial Diagnostics & Root Cause Analysis

Check: CA logs — kubectl logs -n kube-system — it logs exactly why it's not scaling.

  • Pod is unschedulable for a reason other than resources — e.g., node affinity requires a specific label that no node type has. CA won't add nodes it can't schedule the pod on.
  • Max node count reached — CA has a configured max. --max-nodes-total or per-node-group limit.
  • Pod has cluster-autoscaler.kubernetes.io/safe-to-evict: false — CA may refuse to scale if eviction of existing pods is blocked.
  • Cooldown period — CA has a scale-up cooldown (default 10 min). May be waiting.
2️⃣

Remediation & Permanent Safeguards

  • Budget exhausted — cloud account has hit EC2/VM quota.
  • CA can't provision the requested instance type — spot capacity unavailable.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Pod is unschedulable for a reason other than resources — e.g., node affinity requires a specific label that no node type has. CA w."
⚡ 60-Second Elevator Pitch Talking Points
  • Pod is unschedulable for a reason other than resources — e.g., node affinity requires a specific ...
  • Max node count reached — CA has a configured max. --max-nodes-total or per-node-group limit.
  • Pod has cluster-autoscaler.kubernetes.io/safe-to-evict: false — CA may refuse to scale if evictio...
⛔ 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. Restarting a crashing container without examining preceding termination logs via kubectl logs --previous when configuring cluster autoscaler scaling Restarting the pod flushes ephemeral container runtime state, destroying vital panic stack traces and fatal initialization logs.
  2. Misdiagnosing an application boot crash as a failure of aggressive liveness probes when configuring cluster autoscaler scaling Liveness probes with short timeouts or high failure thresholds kill slow-starting applications repeatedly, causing false CrashLoopBackOff loops.
  3. Neglecting node taints, tolerations, and resource quotas when diagnosing pods stuck in Pending when configuring cluster autoscaler scaling Pods remain Pending when scheduler predicates fail; kubectl describe pod reveals whether CPU/memory exhaustion or taints prevent placement.
  4. Invoking kubectl delete pod --force --grace-period=0 indiscriminately on unready pods when configuring cluster autoscaler scaling Forced deletion bypasses kubelet cleanup and can cause multi-attach errors on PersistentVolumes (PVs) or split-brain on stateful workloads.
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 →