autoscaler/cluster-autoscaler
David Morrison cd2db00d20 change kwok nodegroup annotation key 2025-09-17 12:05:56 -07:00
..
apis Merge pull request #8539 from BigDarkClown/update-dep 2025-09-17 07:56:14 -07:00
capacitybuffer Add Capacity Buffer controller logic 2025-09-15 11:05:22 +00:00
cloudprovider change kwok nodegroup annotation key 2025-09-17 12:05:56 -07:00
clusterstate Add tests for NodeGroupScaleUpTime() 2025-08-21 08:30:20 +00:00
config Merge pull request #8057 from MenD32/fix/cooldown-reset-on-pod-redeploy 2025-09-17 06:24:15 -07:00
context
core Merge pull request #8539 from BigDarkClown/update-dep 2025-09-17 07:56:14 -07:00
debuggingsnapshot
estimator nit: when scheduling fails on topology constraints, skip the last node that failed scheduling 2025-06-11 09:38:49 +03:00
expander
hack Update K8S dependency to use 1.34.1 2025-09-12 16:51:08 +00:00
loop
metrics
observers
processors Replace schedulerframework.NodeInfo pointers with fwk.NodeInfo interface 2025-09-15 14:43:38 +00:00
proposals Create a proposal for CapacityBuffers API. 2025-08-11 21:00:47 +02:00
provisioningrequest
simulator Fix unit-tests 2025-09-15 16:16:46 +00:00
utils Merge pull request #8539 from BigDarkClown/update-dep 2025-09-17 07:56:14 -07:00
version Update K8S dependency to use 1.34.1 2025-09-12 16:51:08 +00:00
.gitignore
Dockerfile
FAQ.md Utho autoscaler (#8398) 2025-08-11 09:35:08 -07:00
Makefile Fix CA's command 2025-08-05 16:16:37 +00:00
OWNERS just approver 2025-07-28 09:31:05 -07:00
README.md Add CoreWeave Cluster Autoscaler provider (#8332) 2025-08-11 14:19:07 -07:00
cloudbuild.yaml
go.mod Update K8S dependency to use 1.34.1 2025-09-12 16:51:08 +00:00
go.sum Update K8S dependency to use 1.34.1 2025-09-12 16:51:08 +00:00
main.go Enable DeltaSnapshotStore to work when DRA is enabled 2025-06-11 08:29:53 +00:00
push_image.sh
update_toc.py

README.md

Cluster Autoscaler

Introduction

Cluster Autoscaler is a tool that automatically adjusts the size of the Kubernetes cluster when one of the following conditions is true:

  • there are pods that failed to run in the cluster due to insufficient resources.
  • there are nodes in the cluster that have been underutilized for an extended period of time and their pods can be placed on other existing nodes.

FAQ/Documentation

An FAQ is available HERE.

You should also take a look at the notes and "gotchas" for your specific cloud provider:

Releases

We recommend using Cluster Autoscaler with the Kubernetes control plane (previously referred to as master) version for which it was meant. The below combinations have been tested on GCP. We don't do cross version testing or compatibility testing in other environments. Some user reports indicate successful use of a newer version of Cluster Autoscaler with older clusters, however, there is always a chance that it won't work as expected.

Starting from Kubernetes 1.12, versioning scheme was changed to match Kubernetes minor releases exactly.

Kubernetes Version CA Version Chart Version
1.33.x 1.33.x 9.47.0+
1.32.x 1.32.x 9.45.0+
1.31.x 1.31.x 9.38.0+
1.30.x 1.30.x 9.37.0+
1.29.X 1.29.X 9.35.0+
1.28.X 1.28.X 9.34.0+
1.27.X 1.27.X 9.29.0+
1.26.X 1.26.X 9.28.0+
1.25.X 1.25.X
1.24.X 1.24.X 9.25.0+
1.23.X 1.23.X 9.14.0+
1.22.X 1.22.X
1.21.X 1.21.X 9.10.0+
1.20.X 1.20.X 9.5.0+
1.19.X 1.19.X
1.18.X 1.18.X 9.0.0+
1.17.X 1.17.X
1.16.X 1.16.X
1.15.X 1.15.X
1.14.X 1.14.X
1.13.X 1.13.X
1.12.X 1.12.X
1.11.X 1.3.X
1.10.X 1.2.X
1.9.X 1.1.X
1.8.X 1.0.X
1.7.X 0.6.X
1.6.X 0.5.X, 0.6.X*
1.5.X 0.4.X
1.4.X 0.3.X

*Cluster Autoscaler 0.5.X is the official version shipped with k8s 1.6. We've done some basic tests using k8s 1.6 / CA 0.6 and we're not aware of any problems with this setup. However, Cluster Autoscaler internally simulates Kubernetes' scheduler and using different versions of scheduler code can lead to subtle issues.

Schedule

Cluster Autoscaler releases new minor versions shortly after OSS Kubernetes release and patches for versions corresponding to currently supported Kubernetes versions on a roughly 2 month cadence. Currently planned schedule is below. Please note that target dates listed below are approximate and we expect up to a week difference between target ETA and the actual releases.

Date Maintainer Preparing Release Backup Maintainer Type
2025-06-11 jackfrancis gjtempleton 1.33
2025-07-16 gjtempleton towca patch
2025-08-20 towca BigDarkClown patch
2025-09-17 BigDarkClown x13n 1.34
2025-10-22 x13n jackfrancis patch
2025-11-19 jackfrancis gjtempleton patch

Additional patch releases may happen outside of the schedule in case of critical bugs or vulnerabilities.

Notable changes

For CA 1.1.2 and later, please check release notes.

CA version 1.1.1:

  • Fixes around metrics in the multiple kube apiserver configuration.
  • Fixes for unready nodes issues when quota is overrun.

CA version 1.1.0:

CA version 1.0.3:

  • Adds support for safe-to-evict annotation on pod. Pods with this annotation can be evicted even if they don't meet other requirements for it.
  • Fixes an issue when too many nodes with GPUs could be added during scale-up (https://github.com/kubernetes/kubernetes/issues/54959).

CA Version 1.0.2:

CA Version 1.0.1:

CA Version 1.0:

With this release we graduated Cluster Autoscaler to GA.

  • Support for 1000 nodes running 30 pods each. See: Scalability testing report
  • Support for 10 min graceful termination.
  • Improved eventing and monitoring.
  • Node allocatable support.
  • Removed Azure support. See: PR removing support with reasoning behind this decision
  • cluster-autoscaler.kubernetes.io/scale-down-disabled annotation for marking nodes that should not be scaled down.
  • scale-down-delay-after-delete and scale-down-delay-after-failure flags replaced scale-down-trial-interval

CA Version 0.6:

CA Version 0.5.4:

  • Fixes problems with node drain when pods are ignoring SIGTERM.

CA Version 0.5.3:

CA Version 0.5.2:

CA Version 0.5.1:

CA Version 0.5:

  • CA continues to operate even if some nodes are unready and is able to scale-down them.
  • CA exports its status to kube-system/cluster-autoscaler-status config map.
  • CA respects PodDisruptionBudgets.
  • Azure support.
  • Alpha support for dynamic config changes.
  • Multiple expanders to decide which node group to scale up.

CA Version 0.4:

  • Bulk empty node deletions.
  • Better scale-up estimator based on binpacking.
  • Improved logging.

CA Version 0.3:

  • AWS support.
  • Performance improvements around scale down.

Deployment

Cluster Autoscaler is designed to run on Kubernetes control plane (previously referred to as master) node. This is the default deployment strategy on GCP. It is possible to run a customized deployment of Cluster Autoscaler on worker nodes, but extra care needs to be taken to ensure that Cluster Autoscaler remains up and running. Users can put it into kube-system namespace (Cluster Autoscaler doesn't scale down node with non-mirrored kube-system pods running on them) and set a priorityClassName: system-cluster-critical property on your pod spec (to prevent your pod from being evicted).

Supported cloud providers: