Q: What is the purpose of `podAntiAffinity` with `topologyKey: topology.kubernetes.io/zone`?
This spreads pods across availability zones rather than just across nodes. If your cluster spans 3 AZs (us-east-1a, 1b, 1c), this anti-af...
#Kubernetes #Advanced Scenarios #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. 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
This spreads pods across availability zones rather than just across nodes. If your cluster spans 3 AZs (us-east-1a, 1b, 1c), this anti-affinity ensures no two pods of the same app land in the same AZ. Why: Even with node anti-affinity, all your "different nodes" could be in the same AZ. If that AZ goes down, you lose everything. Zone-spread anti-affinity ensures true high availability across data center failures. Combine with topologySpreadConstraints for finer control over pod distribution across zones and nodes.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: This spreads pods across availability zones rather than just across nodes. If your cluster spans 3 AZs (us-east-1a, 1b, 1c), this ."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: This spreads pods across availability zones rather than just across nodes. If your cluster span
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement