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.
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."
Initial Diagnostics & Root Cause Analysis
- Check pod labels vs service selector —
kubectl describe serviceshows the selector.kubectl get pod --show-labelsshows 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.
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- Check the port mapping — service
targetPortmust match the container's listening port. - Test from inside the cluster —
kubectl exec -itto isolate if it's a network policy or external routing issue.-- curl :
- 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...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Configuring Service selector labels that mismatch underlying Pod manifest metadata when configuring Running reachable Service
A typo in
spec.selectorcauses the Service endpoints list (kubectl get endpoints) to remain empty, resulting in503 Service Unavailableor timeouts. -
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. -
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. - 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.