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
🛠️ Production Runbook & Step-by-Step Resolution
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 —
ExactvsPrefixvsImplementationSpecific.Exactonly matches/api, not/api/users. UsePrefixto 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...
Advertisement