Releases: gardener/autoscaler
Releases · gardener/autoscaler
v0.16.0
[autoscaler]
🏃 Others
- [OPERATOR] Bug fix: Allow scaling down of machine with already lowered priority (#75, @prashanth26)
v0.15.0
[autoscaler]
📰 Noteworthy
- [USER] Enable configuraiton of flags such as
control-apiserver-burst
,control-apiserver-qps
,target-apiserver-burst
,target-apiserver-qps
andmin-resync-period
for kubernetes client configurations while fetching objects for MCM cloud provider. (#73, @prashanth26) - [OPERATOR] Switch to using cached informers to fetch cloud provider details more optimally. (#73, @prashanth26)
v0.14.0
[autoscaler]
🏃 Others
- [USER] Support the latest zone label
topology.kubernetes.io/zone
in addition to the existingfailure-domain.beta.kubernetes.io/zone
while determining the zone for AWS machines. (#70, @prashanth26) - [USER] Allow scaling up from zero using the latest stable zone, region, arch, OS, instanceType labels on node objects. (#70, @prashanth26)
v0.10.1
[autoscaler]
🏃 Others
- [USER] Support scale to/from zero for MCM OOT providers - AWS, Azure. (#66, @prashanth26)
v0.13.0
[autoscaler]
🏃 Others
- [USER] Support scale to/from zero for MCM OOT providers - AWS, Azure. (#65, @prashanth26)
- [OPERATOR] Ignore gardener-specific and csi-specific labels while comparing nodegroups (#62, @hardikdr)
v0.12.0
[autoscaler]
Improvements
- [OPERATOR] MCM provider now also returns unregistered nodes to Autoscaler. This change enables autoscaler to pick up an alternate worker-pool if the chosen one can't be scaled-up. (#58, @jsravn)
- [OPERATOR] Autoscaler avoids scaling down the machines which are already being terminated. (#59, @hardikdr)
v0.11.0
[autoscaler]
Improvements
- [OPERATOR] Rebased cluster autoscaler with upstream and the default branch is now machine-controller-manager-provider.
v0.10.0
cluster-autoscaler-chart-1.0.2
Scales Kubernetes worker nodes within autoscaling groups.