v1.27.3

[gardener/autoscaler]

🐛 Bug Fixes

• [OPERATOR] Fixed a bug where the instance status was nil when machine.Status.LastOperation.Type = Create causing it to not be considered as an unregistered Node and thereby cluster autoscaler never removing it by @rishabh-11 [#309]

Docker Images

• cluster-autoscaler: europe-docker.pkg.dev/gardener-project/releases/gardener/autoscaler/cluster-autoscaler:v1.27.3

v1.29.0

[gardener/autoscaler]

🏃 Others

• [OPERATOR] - Synced changes till v1.29.2 of upstream autoscaler.
  • Updated the log level of some pod scheduling logs for better debugging. by @sssash18 [#302]

Docker Images

• cluster-autoscaler: europe-docker.pkg.dev/gardener-project/releases/gardener/autoscaler/cluster-autoscaler:v1.29.0

v1.28.2

[gardener/autoscaler]

🏃 Others

• [OPERATOR] Updated the log level of some pod scheduling logs for better debugging by @sssash18 [#305]

Docker Images

• cluster-autoscaler: europe-docker.pkg.dev/gardener-project/releases/gardener/autoscaler/cluster-autoscaler:v1.28.2

v1.27.2

[gardener/autoscaler]

⚠️ Breaking Changes

• [OPERATOR] Change OCI Image Registry from GCR (eu.gcr.io/gardener-project) to Artifact-Registry (europe-docker.pkg.dev/gardener-project/releases). Users should update their references.
  by @ccwienk [#296]

🏃 Others

• [OPERATOR] Updated the log level of some pod scheduling logs for better debugging by @sssash18 [#306]

Docker Images

• cluster-autoscaler: europe-docker.pkg.dev/gardener-project/releases/gardener/autoscaler/cluster-autoscaler:v1.27.2

v1.28.1

[gardener/autoscaler]

🏃 Others

• [OPERATOR] Add logging for mcm cloud-provider methods for better traceability by @rishabh-11 [#301]

Docker Images

• cluster-autoscaler: europe-docker.pkg.dev/gardener-project/releases/gardener/autoscaler/cluster-autoscaler:v1.28.1

1.0.0

vpa-1.0.0

Release 1.0.0

v1.28.0

[gardener/autoscaler]

⚠️ Breaking Changes

• [OPERATOR] Change OCI Image Registry from GCR (eu.gcr.io/gardener-project) to Artifact-Registry (europe-docker.pkg.dev/gardener-project/releases). Users should update their references.
  by @ccwienk [#269]

✨ New Features

• [OPERATOR] Autoscaler will now add NodeGroupAutoscalingOptions to node groups from annotations present in its corresponding machineDeployments by @aaronfern [#257]

🏃 Others

• [OPERATOR] Synced changes till v1.28.0 of upstream autoscaler by @aaronfern [#260]
• [OPERATOR] CA will not scale down machine deployment due to a machine in failed phase, this prevents the race condition which was leading to deletion of a new healthy machine. by @sssash18 [#291]
• [OPERATOR] Cluster Autoscaler will suspend its activities if the machine-controller-manager is offline by @sssash18 [#256]

Docker Images

• cluster-autoscaler: europe-docker.pkg.dev/gardener-project/releases/gardener/autoscaler/cluster-autoscaler:v1.28.0

v1.27.1

[gardener/autoscaler]

✨ New Features

• [USER] Gardener autoscaler now backs-off early from a node-group (i.e. machinedeployment) in case of ResourceExhausted error. Refer docs at https://github.com/gardener/autoscaler/blob/machine-controller-manager-provider/cluster-autoscaler/FAQ.md#when-does-autoscaler-backs-off-early-from-a-node-group for details. by @himanshu-kun [#253]
• [DEVELOPER] unit tests framework introduced to test implemented methods of Cloudprovider and Nodegroup interface by @rishabh-11 [#215]

🐛 Bug Fixes

• [OPERATOR] A bug where MCM removed a machine other than the one , CA wanted , is resolved. by @rishabh-11 [#215]

🏃 Others

• [OPERATOR] Initial implementation for Refresh() method of CloudProvider interface done by @rishabh-11 [#215]
• [OPERATOR] machinepriority.machine.sapcloud.io annotation on machine is now reset to 3 by autoscaler if the corresponding node doesn't have ToBeDeletedByClusterAutoscaler taint by @rishabh-11 [#215]

v1.27.0

[autoscaler]

🐛 Bug Fixes

• [USER] Bug where deadline for machineDeployment fetch/update was not respected is resolved. Due to this bug , bulk removal of empty nodes was getting blocked, which in turn, blocked scale-ups for pending pods (gardener/autoscaler#216, @himanshu-kun)
• [OPERATOR] If priority expander specified, but config map not deployed in kube-system namespace of shoot , then warning log in autoscaler logs printed. (gardener/autoscaler#196, @himanshu-kun)

🏃 Others

• [OPERATOR] Gardener autoscaler version is shown in logs of CA , earlier only upstream autoscaler version was shown (gardener/autoscaler#216, @himanshu-kun)
• [OPERATOR] Synced the changes till v1.27.1 of upstream autoscaler. (gardener/autoscaler#225, @ashwani2k)
• [OPERATOR] k8s.io/klog is no longer imported by the cluster-autoscaler. k8s.io/klog/v2 is used instead in a consistent manner. (gardener/autoscaler#231, @ialidzhikov)

v1.26.2

[autoscaler]

🐛 Bug Fixes

• [USER] Bug where deadline for machineDeployment fetch/update was not respected is resolved. Due to this bug , bulk removal of empty nodes was getting blocked, which in turn, blocked scale-ups for pending pods (gardener/autoscaler#222, @himanshu-kun)

🏃 Others

• [OPERATOR] Gardener autoscaler version is shown in logs of CA , earlier only upstream autoscaler version was shown (gardener/autoscaler#222, @himanshu-kun)