1374af2b79
AWS Scaling from/to 0, extract GPU information |
||
|---|---|---|
| .. | ||
| Godeps | ||
| cloudprovider | ||
| clusterstate | ||
| config | ||
| core | ||
| deploy | ||
| estimator | ||
| expander | ||
| metrics | ||
| proposals | ||
| simulator | ||
| utils | ||
| vendor | ||
| .gitignore | ||
| Dockerfile | ||
| FAQ.md | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| fix_gopath.sh | ||
| main.go | ||
| run.sh | ||
| update_toc.py | ||
| version.go | ||
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:
- Allows scaling node groups to 0 (currently only in GCE/GKE, other cloud providers are coming). See: How can I scale a node group to 0?
- Price-based expander (currently only in GCE/GKE, other cloud providers are coming). See: What are Expanders?
- Similar node groups are balanced (to be enabled with a flag). See: I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?
- It is possible to scale-down nodes with kube-system pods if PodDisruptionBudget is provided. See: How can I scale my cluster to just 1 node?
- Automatic node group discovery on AWS (to be enabled with a flag). See: AWS doc.
- CA exposes runtime metrics. See: How can I monitor Cluster Autoscaler?
- CA exposes an endpoint for liveness probe.
- max-grateful-termination-sec flag renamed to max-graceful-termination-sec.
- Lower AWS API traffic to DescribeAutoscalingGroup.
CA Version 0.5.4:
- Fixes problems with node drain when pods are ignoring SIGTERM.
CA Version 0.5.3:
- Fixes problems with pod anti-affinity in scale up https://github.com/kubernetes/autoscaler/issues/33.
CA Version 0.5.2:
- Fixes problems with pods using persistent volume claims in scale up https://github.com/kubernetes/contrib/issues/2507.
CA Version 0.5.1:
- Fixes problems with slow network route creations on cluster scale up https://github.com/kubernetes/kubernetes/issues/43709.
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: