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

Q: Your Ingress is returning 404 for a path that you've configured. What do you check?

1. Check the Ingress resource — kubectl describe ingress <name> — verify the path and service name are correct.

#Kubernetes #Networking #L2 #Container Orchestration #K8s #Ingress
🎙️ 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

  • Check the Ingress resource — kubectl describe ingress — verify the path and service name are correct.
  • Check the IngressClass — does the Ingress have the right ingressClassName? If multiple controllers exist (nginx, traefik), the wrong one might be handling it.
  • Check path type — Exact vs Prefix vs ImplementationSpecific. Exact only matches /api, not /api/users. Use Prefix to match all subpaths.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Check backend service — is the service name and port correct? Does the service have endpoints?
  • Ingress controller logs — kubectl logs -n ingress-nginx — nginx logs will show 404 details.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Check the Ingress resource — kubectl describe ingress — verify the path and service name are correct.."
⚡ 60-Second Elevator Pitch Talking Points
  • Check the Ingress resource — kubectl describe ingress — verify the path and service name are cor...
  • Check the IngressClass — does the Ingress have the right ingressClassName? If multiple controller...
  • Check path type — Exact vs Prefix vs ImplementationSpecific. Exact only matches /api, not /api/us...
⛔ 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 Ingress returning path 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 Ingress returning path 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 Ingress returning path 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 Ingress returning path 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 →