autoscaler/cluster-autoscaler
Aleksandra Malinowska 4c31a57374 fix leaking taints in case of cloud provider error on node deletion 2017-09-22 17:55:48 +02:00
..
Godeps Godeps update for CA 2017-09-08 14:56:39 +02:00
cloudprovider Cloudprovider/gce/gce_cloud_provider.go unit tests. 2017-09-20 07:57:43 +02:00
clusterstate Log event on scale-up timeout 2017-09-01 14:19:14 +02:00
config respect minimum cores/memory limit during scale down 2017-09-13 10:10:47 +02:00
core fix leaking taints in case of cloud provider error on node deletion 2017-09-22 17:55:48 +02:00
deploy bump container image version to 0.6.0 2017-08-09 16:03:09 -07:00
estimator Small optimize code 2017-09-04 23:50:45 +03:00
expander Do not return error from exist 2017-09-01 00:24:01 +02:00
metrics Set verbosity for each of the glog.Info logs 2017-09-01 12:34:29 +02:00
proposals Small optimize code 2017-09-04 23:50:45 +03:00
simulator Merge pull request #310 from krzysztof-jastrzebski/core-test 2017-09-07 17:15:58 +05:30
utils Keep graceful termination timeout consistent 2017-09-21 12:54:11 +02:00
vendor Add Sirupsen 2017-09-08 14:56:46 +02:00
.gitignore Cluster-Autoscaler - Kubernetes client deps 2016-04-20 11:49:38 +02:00
Dockerfile cluster-autoscaler: Add ca-certificates to the docker image 2017-05-09 12:30:59 +09:00
FAQ.md Describe scale down disabled annotation in Cluster Autoscaler FAQ 2017-09-07 15:31:08 +02:00
Makefile Test-in-docker in CA Makefile 2017-09-05 11:47:01 +02:00
OWNERS Make assignees approvers and reviewers 2016-12-14 16:42:04 -08:00
README.md Add note about running CA 0.6 with k8s 1.6 2017-07-04 16:28:10 +02:00
fix_gopath.sh A simple script to update k8s staging deps and remove vendor dirs 2017-08-18 00:10:44 +02:00
main.go Introduce new flags to control scale down behavior: scale-down-delay-after-delete and scale-down-delay-after-failure, replacing scale-down-trial-interval. scale-down-delay-after-add replaces scale-down-delay 2017-09-18 17:09:44 -07:00
run.sh Cluster-Autoscaler: added wrapper script to pass signals 2017-02-28 17:39:29 +01:00
update_toc.py Fix update_toc.py script to stop appending empty lines 2017-06-30 14:18:18 +02:00
version.go Bump CA version to 0.7.0-beta1 2017-09-13 13:51:33 +02:00

README.md

Cluster Autoscaler

Introduction

Cluster Autoscaler is a tool that automatically adjusts the size of the Kubernetes cluster when:

  • there are pods that failed to run in the cluster due to insufficient resources.
  • some nodes in the cluster are so underutilized, for an extended period of time, that they can be deleted and their pods will be easily placed on some other, existing nodes.

FAQ/Documentation

Is available HERE.

Releases

We strongly recommend using Cluster Autoscaler with version for which it was meant. We don't do ANY cross version testing so if you put the newest Cluster Autoscaler on an old cluster there is a big chance that it won't work as expected.

Kubernetes Version CA Version
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, CA internally simulates k8s scheduler and using different versions of scheduler code can lead to subtle issues.

Notable changes

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 runs on the Kubernetes master node (at least in the default setup on GCE and GKE). It is possible to run customized Cluster Autoscaler inside of the cluster but then extra care needs to be taken to ensure that Cluster Autoscaler is up and running. User can put it into kube-system namespace (Cluster Autoscaler doesn't scale down node with non-manifest based kube-system pods running on them) and mark with scheduler.alpha.kubernetes.io/critical-pod annotation (so that the rescheduler, if enabled, will kill other pods to make space for it to run).

Right now it is possible to run Cluster Autoscaler on: