Q: How do you expose a gRPC service in Kubernetes?
Use a Service with the correct port and protocol annotation. For Ingress: you need an ingress controller that supports gRPC (nginx-ingres...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L2 #Container Orchestration #K8s #Ingress
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. 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️⃣
Production Solution & Architecture
Use a Service with the correct port and protocol annotation. For Ingress: you need an ingress controller that supports gRPC (nginx-ingress with nginx.ingress.kubernetes.io/backend-protocol: GRPC annotation, or Istio). gRPC requires HTTP/2, so TLS is typically required. With Istio: define a VirtualService with gRPC routing rules.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Use a Service with the correct port and protocol annotation. For Ingress: you need an ingress controller that supports gRPC (nginx."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Use a Service with the correct port and protocol annotation. For Ingress: you need an ingress c
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement