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

Q: A pod is `Running` but your app is not reachable via the Service. What do you check?

Check pod labels vs service selector — kubectl describe service shows the selector. kubectl get pod --show-labels shows pod labels. They must match exactly.

#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: Service-to-pod connectivity debugging.. 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: Service-to-pod connectivity debugging.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

  • Check pod labels vs service selector — kubectl describe service shows the selector. kubectl get pod --show-labels shows pod labels. They must match exactly.
  • Check endpoints — kubectl get endpoints . If it shows , the selector doesn't match any pod.
  • Check if the pod is Ready — even if Running, if the readiness probe fails, the pod is removed from endpoints.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Check the port mapping — service targetPort must match the container's listening port.
  • Test from inside the cluster — kubectl exec -it -- curl : to isolate if it's a network policy or external routing issue.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Check pod labels vs service selector — kubectl describe service shows the selector. kubectl get pod --show-labels shows pod label."
⚡ 60-Second Elevator Pitch Talking Points
  • Check pod labels vs service selector — kubectl describe service shows the selector. kubectl get ...
  • Check endpoints — kubectl get endpoints . If it shows , the selector doesn't match any pod.
  • Check if the pod is Ready — even if Running, if the readiness probe fails, the pod is removed fro...
⛔ 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 Running reachable Service 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 Running reachable Service 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 Running reachable Service 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 Running reachable Service 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 →