Q: DNS resolution is failing inside your cluster. Pods can't resolve service names. What do you check?
1. kubectl get pods -n kube-system | grep coredns — is CoreDNS running?
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 one of our high-traffic production clusters, our SRE team handled this incident using a standardized runbook. 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."
Initial Diagnostics & Root Cause Analysis
kubectl get pods -n kube-system | grep coredns— is CoreDNS running?kubectl logs -n kube-system— any errors?- Test DNS from inside a pod:
kubectl exec -it— this should always resolve.-- nslookup kubernetes.default
Remediation & Permanent Safeguards
- Check
resolv.confinside the pod:kubectl exec -it— should point to the cluster DNS IP.-- cat /etc/resolv.conf - Check CoreDNS ConfigMap:
kubectl get configmap coredns -n kube-system -o yaml— misconfigured forwarders can break external DNS resolution.
- kubectl get pods -n kube-system | grep coredns — is CoreDNS running?
- kubectl logs -n kube-system — any errors?
- Test DNS from inside a pod: kubectl exec -it -- nslookup kubernetes.default — this should always...
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 resolution failing inside
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 resolution failing inside
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 resolution failing inside
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 resolution failing inside Verifying EndpointSlice population immediately determines whether a connectivity failure is caused by pod labeling, readiness probes, or routing.