⚡ ~/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 23 of 207 in Kubernetes
Senior DevOps / SRE [L2] Kubernetes Troubleshooting & Debugging Production Scenario [L2]
🎯 Target Role / Context: Kubernetes Scenario #9 (L2) · Troubleshooting & Debugging

Q: You run `kubectl exec -it <pod> -- bash` and get "container not found." What's wrong?

If a pod has multiple containers, you need to specify which one:

#Kubernetes #Troubleshooting & Debugging #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. The interviewer is testing: Multi-container pod awareness.. 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: "In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. The interviewer is testing: Multi-container pod awareness.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Production Solution & Architecture

If a pod has multiple containers, you need to specify which one: Get container names with: kubectl get pod -o jsonpath='{.spec.containers[*].name}' Also — some minimal images (Alpine, distroless) don't have bash. Try sh instead.

kubectl exec -it <pod> -c <container-name> -- bash
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: If a pod has multiple containers, you need to specify which one:."
⚡ 60-Second Elevator Pitch Talking Points
  • Immediate Triage: If a pod has multiple containers, you need to specify which one:
  • Run targeted verification commands before modifying configuration.
  • Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
⛔ 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 kubectl exec bash 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 kubectl exec bash 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 kubectl exec bash 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 kubectl exec bash 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 →