Q: What is Pod Topology Spread Constraints and how is it different from `podAntiAffinity`?
Both spread pods across topology domains (nodes, zones).
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "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."
Production Solution & Architecture
Both spread pods across topology domains (nodes, zones). podAntiAffinity: binary — either pods can or can't be on the same node. Doesn't control HOW spread out they are. Topology Spread Constraints: specifies maxSkew — the maximum difference in pod count between any two topology domains. maxSkew: 1 means: never have more than 1 extra pod in one zone vs another. More granular control for even distribution. Example: 10 pods across 3 zones. With maxSkew: 1: could be 4/3/3. Anti-affinity would just say "no two pods on same node" which doesn't ensure zone balance.
- Immediate Triage: Both spread pods across topology domains (nodes, zones).
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring Topology Spread Constraints Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring Topology Spread Constraints
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring Topology Spread Constraints Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring Topology Spread Constraints Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.