The New Stack: Why Kubernetes autoscalers keep fighting each other (and why the solution must be autonomous)
The article argues that Kubernetes autoscalers such as HPA, VPA, KEDA and Karpenter act on overlapping variables and can conflict, for example VPA shrinking requests that pushes HPA to scale out, or Argo CD reverting HPA replica changes. It describes four collision patterns and proposes a unified control layer that jointly decides replicas, resource requests and node capacity. The piece presents no new measured data beyond an illustrative example and a cited cluster CPU utilization figure of about 8%.
What changes for platform teams
Platform teams running HPA, VPA, KEDA or Karpenter together should check for overlapping writes to replicas and resource requests, and for GitOps auto-sync reverting autoscaler changes. The article offers no shipped tooling, so nothing changes in existing tools today.
Read the original at The New Stack ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules