21Some nodes are at 90% and others are idle. Why does the scheduler allow this, and how do you fix it?▼hardUberDatabricksRed Hat2 notes & comments○ sign inThe scheduler is behaving correctly, which is the part that confuses people. It optimises placement at admission time and never revisits, so a cluster drifts out of balance by design.Open full answer →
47We run three zones and after every incident the recovered zone sits half empty. How do you spread workloads deliberately?▼mediumUberFlipkartWalmart Global Tech◆ premiumAnti-affinity is binary and falls over at scale; topologySpreadConstraints give you numeric skew control across labeled domains. The subtle parts are eligibility filtering before the skew math, and the fact that Kubernetes never rebalances anything for you.Open full answer →
