A pod has been Pending for an hour with 'volume node affinity conflict' and there is spare capacity everywhere. Explain it.

The volume is in one availability zone and the scheduler cannot move it. Spare capacity in the other two zones is not spare capacity for this pod, and no amount of scaling helps.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

The volume is in one availability zone and the scheduler cannot move it. Spare capacity in the other two zones is not spare capacity for this pod, and no amount of scaling helps.

28 answers per topic instead of 18, and your progress kept · no cardor unlock all 386 remaining answers · ₹2,000 / $25

UP NEXT ON YOUR JOURNEY

Next in this trackGreen Health Checks, Broken App Next in this trackFive DNS Lookups Per Call Next in this trackAn Autoscaler That Thrashes

DISCUSSION · 0

Nothing here yet. Say how you would answer it.