⚡ ~/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 39 of 207 in Kubernetes
Staff SRE / Principal Architect [L3] Kubernetes Networking Staff SRE Scenario [L3]
🎯 Target Role / Context: Kubernetes Scenario #26 (L3) · Networking

Q: A request is going from Pod A to Pod B via a Service and it's very slow. How do you troubleshoot network latency in Kubernetes?

1. Baseline test — kubectl exec -it <pod-a> -- curl -o /dev/null -s -w "%{time_total}" http://<service>:<port> to measure actual latency.

#Kubernetes #Networking #L3 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. 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: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. 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

  • Baseline test — kubectl exec -it -- curl -o /dev/null -s -w "%{time_total}" http://: to measure actual latency.
  • Bypass the service — test pod-to-pod directly using the pod IP to see if latency is in kube-proxy/iptables: kubectl exec -it -- curl http://:.
  • Check kube-proxy mode — iptables vs ipvs. ipvs is faster at scale.
  • Check CNI — network plugin issues. Run ping between pods to test raw network latency.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • DNS latency — kubectl exec -it -- time nslookup — DNS lookups through CoreDNS add latency. Consider ndots:5 setting impact.
  • Node-level network — check if nodes are on the same AZ. Cross-AZ traffic adds ~1-2ms.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Baseline test — kubectl exec -it -- curl -o /dev/null -s -w "%{time_total}" http://: to measure actual latency.."
⚡ 60-Second Elevator Pitch Talking Points
  • Baseline test — kubectl exec -it -- curl -o /dev/null -s -w "%{time_total}" http://: to measure ...
  • Bypass the service — test pod-to-pod directly using the pod IP to see if latency is in kube-proxy...
  • Check kube-proxy mode — iptables vs ipvs. ipvs is faster at scale.
⛔ 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 request going 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 request going 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 request going 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 request going 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 →