Q: You have a Kubernetes cluster in two regions for disaster recovery. How do you sync workloads?
Use GitOps (ArgoCD) with a shared Git repository. Both clusters sync from the same manifests repo. Each cluster has its own ArgoCD instan...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L2 #Container Orchestration #K8s #ArgoCD
🎙️ 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️⃣
Production Solution & Architecture
Use GitOps (ArgoCD) with a shared Git repository. Both clusters sync from the same manifests repo. Each cluster has its own ArgoCD instance. If primary cluster fails: the DR cluster already has all the workload definitions; just ensure the workloads are running (they might be scaled to 0 in DR to save cost, scale them up). For data: use database replication (Aurora Global, DynamoDB Global Tables). For traffic: Route 53 health checks with failover routing. If primary endpoint goes down, Route 53 automatically routes to DR cluster.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Use GitOps (ArgoCD) with a shared Git repository. Both clusters sync from the same manifests repo. Each cluster has its own ArgoCD."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Use GitOps (ArgoCD) with a shared Git repository. Both clusters sync from the same manifests re
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement