Q: How do you implement multi-cluster service discovery so Service A in cluster 1 can call Service B in cluster 2?
Options:
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L3 #Container Orchestration #K8s #VPC
🎙️ 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
Options:
- Submariner — CNCF project. Creates IPsec tunnels between clusters, enables pod-to-pod communication across clusters.
- Istio multi-cluster — Istio service mesh spanning multiple clusters with shared control plane or separate control planes with federation.
- AWS Cloud Map + Route 53 — register services from both clusters in Cloud Map. Use DNS for discovery.
2️⃣
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- External Ingress — expose Service B via Ingress/NLB in cluster 2. Service A calls it via the external DNS name. Simple but requires internet or VPC peering.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Submariner — CNCF project. Creates IPsec tunnels between clusters, enables pod-to-pod communication across clusters.."
⚡ 60-Second Elevator Pitch Talking Points
- Submariner — CNCF project. Creates IPsec tunnels between clusters, enables pod-to-pod communicati...
- Istio multi-cluster — Istio service mesh spanning multiple clusters with shared control plane or ...
- AWS Cloud Map + Route 53 — register services from both clusters in Cloud Map. Use DNS for discovery.
Advertisement