v1.21.5

[autoscaler]

🐛 Bug Fixes

• [USER] Autoscaler would not scale-down if the node-grp(i.e. machineDeployment) is under rolling update. (gardener/autoscaler#209, @himanshu-kun)
  • Logic of fixing up the node grp size for node grp, whose current size not equals expected size for long time , is also disabled.
• [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#201, @himanshu-kun)

v1.26.0

[autoscaler]

🐛 Bug Fixes

• [USER] Autoscaler would not scale-down if the node-grp(i.e. machineDeployment) is under rolling update. (gardener/autoscaler#160, @himanshu-kun)
  • Logic of fixing up the node grp size for node grp, whose current size not equals expected size for long time , is also disabled.

📖 Documentation

• [USER] We advise not to use this version but v1.26.1 , as the upstream v1.26.0 crashes due to a bug , which is fixed in 1.26.1 . We have synced this version to keep in line with the syncing procedure which has been followed till now. (gardener/autoscaler#184, @elankath)
• [DEVELOPER] vendored packages are excluded from checkmarx scans (gardener/autoscaler#169, @zkdev)
• [DEVELOPER] cloud providers other than MCM are excluded from checkmarx scans. (gardener/autoscaler#170, @rishabh-11)

🏃 Others

• [OPERATOR] Synced the changes till v1.26.0 of upstream autoscaler (gardener/autoscaler#184, @elankath)
  • mcmCloudProvider now implements new method: HasInstance(*apiv1.Node) (bool, error) . Currently basic implementation in place.
• [OPERATOR] FAQ update/Issue template introduced for sync with upstream autoscaler (gardener/autoscaler#188, @elankath)
• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#161, @oliver-goetz)
  • Update Go version to 1.19.5.
• [DEVELOPER] Nodes present in the cluster prior to IT would now be tainted with taint testing.node.gardener.cloud/initial-node-blocked. This taint is removed once IT finishes (pass or fail) (gardener/autoscaler#187, @himanshu-kun)

v1.25.1

[autoscaler]

🏃 Others

• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#162, @oliver-goetz)
  • Update Go version to 1.19.5.

v1.24.1

[autoscaler]

🏃 Others

• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#164, @oliver-goetz)
  • Update Go version to 1.18.10.

v1.23.2

[autoscaler]

🏃 Others

• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#165, @oliver-goetz)
  • Update Go version to 1.18.10.

v1.22.4

[autoscaler]

🏃 Others

• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#166, @oliver-goetz)
  • Update Go version to 1.18.10.

v1.21.4

[autoscaler]

🏃 Others

• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#167, @oliver-goetz)
  • Update Go version to 1.18.10.

v1.20.4

[autoscaler]

🏃 Others

• [DEVELOPER] Docker images for cluster-autoscaler are published with multi-arch support for linux/amd64 and linux/arm64 now. (gardener/autoscaler#168, @oliver-goetz)
  • Update Go version to 1.18.10.

v1.25.0

[autoscaler]

🏃 Others

• [OPERATOR] Synced the changes till v1.25.0 of upstream autoscaler (gardener/autoscaler#157, @rishabh-11)

v1.24.0

[autoscaler]

🐛 Bug Fixes

• [USER] Bug stopping autoscaler to run because of architecture incompatibility is fixed (gardener/autoscaler#147, @himanshu-kun)

🏃 Others

• [OPERATOR] Synced the changes till v1.24.0 of upstream autoscaler (gardener/autoscaler#152, @rishabh-11)