DevOps Daily with Fexingo · 2026-07-04 · 9 min
Kubernetes cluster autoscaler is a workhorse for dynamic workloads, but when you're running spot (preemptible) instances, the node autoscaler's default behavior can actually hurt reliability. In this episode, Lucas and Luna break down a real incident from a large ad-tech platform running 2,000+ nodes on AWS EC2 Spot Instances. When spot interruption rates spiked during a regional AZ outage, the cluster autoscaler's rigid scale-down logic kept terminating nodes that were seconds away from stabilizing, causing a cascading re-scheduling loop that nearly took down their real-time bidding service. They walk through the specific configuration failures: the unbound scale-down-delay-after-add, the lack of node disruption budgets for spot pools, and the missing mixed-instance-policy fallback. Plus, they share the three YAML changes that fixed it - including custom priority expander logic and a proactive node-drain webhook. If you're running spot nodes in production, this is the episode that will save you from a 2 AM pager.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.