autoscaler/cluster-autoscaler
Austin Siu 32f10ebff5 Update go.mod with new net dependency 2022-07-12 17:53:21 -05:00
..
cloudprovider Update imports and add instructions for vendored code 2022-07-12 17:53:20 -05:00
clusterstate Fixing test case for DeletedNodes. 2022-05-17 12:54:53 -07:00
config Limit binpacking based on #new_nodes or time 2022-06-20 17:02:51 +02:00
context add a flag to allow event duplication 2022-06-03 14:26:38 -04:00
core Merge pull request #4896 from fookenc/master 2022-07-04 05:13:24 -07:00
debuggingsnapshot CA: Debugging snapshotter locking optimisation for better transactions 2022-01-27 11:36:19 +00:00
estimator Check if pods fit on the new node in binpacking 2022-06-20 17:02:51 +02:00
expander add starter code and readme for grpc expander usage 2022-02-16 12:36:37 -08:00
hack Minor bugfix to update-vendor script 2022-04-07 18:35:34 +02:00
metrics Limit caching pods per owner reference 2022-03-15 10:03:04 +01:00
processors Add nodeTemplate annotations to node annotations 2022-06-03 16:12:16 +00:00
proposals Merge pull request #4134 from airbnb/es--expander-plugin-proposal 2022-07-10 13:57:47 -07:00
simulator switched policy for PodDisruptionBudget from v1beta1 to v1 in time for 1.25 2022-06-24 19:13:03 +02:00
utils switched policy for PodDisruptionBudget from v1beta1 to v1 in time for 1.25 2022-06-24 19:13:03 +02:00
vendor Update go.mod with new net dependency 2022-07-12 17:53:21 -05:00
version Vendor Update to K8s v1.25.0-alpha.0 2022-05-05 12:54:55 +00:00
.gitignore add arch specific cluster-autoscaler targets to gitignore 2021-03-03 16:05:40 -05:00
Dockerfile.amd64 feat: use non-root user for base-image 2022-03-11 23:24:18 +01:00
Dockerfile.arm64 feat: use non-root user for base-image 2022-03-11 23:24:18 +01:00
FAQ.md add a flag to allow event duplication 2022-06-03 14:26:38 -04:00
Makefile Merge pull request #3863 from elmiko/remove-extra-build-cmd 2021-03-11 06:24:24 -08:00
OWNERS Cluster Autoscaler: remove vivekbagade, add towca as an approver in OWNERS 2021-04-27 16:00:09 +02:00
README.md Update guide line documentation for cluster-autoscaler supported cloud providers 2022-06-22 11:07:21 +08:00
cloudbuild.yaml
go.mod Update go.mod with new net dependency 2022-07-12 17:53:21 -05:00
go.sum update cloud-provider-azure version for azure imports 2022-07-06 17:19:46 -07:00
main.go Limit binpacking based on #new_nodes or time 2022-06-20 17:02:51 +02:00
main_test.go
push_image.sh CA - Push Image script - Support newer docker versions 2022-06-14 17:03:50 +01:00
update_toc.py Migrate CA off python2 to python3 2022-03-14 12:52:32 +00:00

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
1.22.X 1.22.X
1.21.X 1.21.X
1.20.X 1.20.X
1.19.X 1.19.X
1.18.X 1.18.X
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.

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: