0.8.0

[autoscaler]

Improvements

• [USER] Add configurable delay for pod age before considering for scale-up (#33, @hardikdr)
• [OPERATOR] Update azure instance types in cluster-autoscaler. (#41, @hardikdr)
• [OPERATOR] Updated the AWS-instance types used cluster autoscaler. (#40, @hardikdr)
• [OPERATOR] Cluster Autoscaler ignores the worker pools with maxSize set to 0. (#39, @hardikdr)
• [OPERATOR] Autoscaler uses zone-information while scaling-up the node-group from zero (#38, @hardikdr)

0.7.1

[autoscaler]

Improvements

• [OPERATOR] Avoid checking controller references while draining nodes (#45, @prashanth26)

0.7.0

[autoscaler]

Improvements

• [USER] Cluster Autoscaler now supports scale to/from 0 for MCM provider (applicable to only AWS & Azure for now) (#26, @rewiko)
• [USER] Cluster Autoscaler skips the nodes not managed by MCM. (#25 , @rewiko)

0.6.0

[autoscaler]

Improvements

• [OPERATOR] Ignore worker specific labels and 128Ki of memory difference while balancing nodegroups. (#23, @hardikdr)

0.5.0

[autoscaler]

Improvements

• [OPERATOR] Fixed issues while syncing annotations/labels/taints maintained on worker-pools (machine-deployments) (#21, @hardikdr)

0.4.0

no release notes available

0.3.0

Release Notes

• The autoscaler has been rebased with the upstream and now vendors 1.12
• Bugfix: Tried to taint/delete more than required nodes while scale down has been fixed #10

Docker image: eu.gcr.io/gardener-project/gardener/autoscaler/cluster-autoscaler:0.3.0

0.2.0

Release Notes

• Supports CI scripts for building, checking and testing

Docker image: eu.gcr.io/gardener-project/gardener/autoscaler/cluster-autoscaler:0.2.0

Cluster Autoscaler with MCM support v0.1.0

Release Notes

• This release integrates support for gardener/machine-controller-manager as a new cloud provider.
• This means that cluster autoscaler now supports AWS, Azure, GCP and OpenStack by making use of machine-controller-manager

Docker image: eu.gcr.io/gardener-project/gardener/autoscaler/cluster-autoscaler:0.1.0