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

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?

#Kubernetes #Networking #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""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.""
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 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."

1️⃣

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 -- nslookup kubernetes.default — this should always resolve.
2️⃣

Remediation & Permanent Safeguards

  • Check resolv.conf inside the pod: kubectl exec -it -- cat /etc/resolv.conf — should point to the cluster DNS IP.
  • Check CoreDNS ConfigMap: kubectl get configmap coredns -n kube-system -o yaml — misconfigured forwarders can break external DNS resolution.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: kubectl get pods -n kube-system | grep coredns — is CoreDNS running?."
⚡ 60-Second Elevator Pitch Talking Points
  • 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...
⛔ 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 resolution failing inside 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 resolution failing inside 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 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.
  4. 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.
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 →