Kubernetes - Scheduling
How can you combine node affinity and pod anti-affinity to ensure pods run on nodes labeled
ssd=true but never on the same node as pods labeled app=db?How can you combine node affinity and pod anti-affinity to ensure pods run on nodes labeled ssd=true but never on the same node as pods labeled app=db?
hard📝 Workflow Q9 of 15
Step-by-Step Solution
Solution:
Step 1: Set node affinity for nodes with ssd=true
Use requiredDuringSchedulingIgnoredDuringExecution nodeAffinity to ensure pods only run on nodes labeled ssd=true.Step 2: Set pod anti-affinity to avoid co-locating with app=db pods
Use requiredDuringSchedulingIgnoredDuringExecution podAntiAffinity with label app=db and topologyKey kubernetes.io/hostname to prevent same node placement.Final Answer:
Use requiredDuringSchedulingIgnoredDuringExecution nodeAffinity for ssd=true and requiredDuringSchedulingIgnoredDuringExecution podAntiAffinity for app=db with hostname topologyKey -> Option BQuick Check:
Combine required nodeAffinity + podAntiAffinity for strict placement [OK]
Quick Trick: Combine required nodeAffinity and podAntiAffinity for strict rules [OK]
Common Mistakes:
- Mixing podAffinity with nodeAffinity incorrectly
- Using preferred instead of required for strict rules
- Confusing nodeAntiAffinity with podAntiAffinity
Master "Scheduling" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes