v1.25.3

[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#221, @himanshu-kun)
• [USER] Removes taints from all nodes to allow for reevaluation during restarts. (gardener/autoscaler#221, @himanshu-kun)

🏃 Others

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

v1.24.3

[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#220, @himanshu-kun)
• [USER] Removes taints from all nodes to allow for reevaluation during restarts. (gardener/autoscaler#220, @himanshu-kun)

🏃 Others

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

v1.23.4

[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#219, @himanshu-kun)
• [USER] Removes taints from all nodes to allow for reevaluation during restarts. (gardener/autoscaler#219, @himanshu-kun)

🏃 Others

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

v1.22.6

[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#218, @himanshu-kun)
• [USER] Removes taints from all nodes to allow for reevaluation during restarts. (gardener/autoscaler#218, @himanshu-kun)

🏃 Others

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

v1.21.6

[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#217, @himanshu-kun)
• [USER] Removes taints from all nodes to allow for reevaluation during restarts. (gardener/autoscaler#217, @himanshu-kun)

🏃 Others

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

v1.25.2

[autoscaler]

🐛 Bug Fixes

• [USER] Autoscaler would not scale-down if the node-grp(i.e. machineDeployment) is under rolling update. (gardener/autoscaler#205, @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#199, @himanshu-kun)

v1.26.1

[autoscaler]

🏃 Others

• [OPERATOR] Synced the changes till v1.26.1 of upstream autoscaler release branch: cluster-autoscaler-release-1.26 (gardener/autoscaler#195, @elankath)
  • Includes fix for kubernetes#5378
• [OPERATOR] Synced the changes till v1.26.2 of upstream autoscaler release branch: cluster-autoscaler-release-1.26 (gardener/autoscaler#212, @elankath)
  • Includes fix for kubernetes#5372
• [OPERATOR] Print warning log if expander=priority and cluster-autoscaler-priority-expander configmap not deployed in kube-system namespace (gardener/autoscaler#203, @himanshu-kun)

v1.24.2

[autoscaler]

🐛 Bug Fixes

• [USER] Autoscaler would not scale-down if the node-grp(i.e. machineDeployment) is under rolling update. (gardener/autoscaler#206, @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#198, @himanshu-kun)

v1.23.3

[autoscaler]

🐛 Bug Fixes

• [USER] Autoscaler would not scale-down if the node-grp(i.e. machineDeployment) is under rolling update. (gardener/autoscaler#207, @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#197, @himanshu-kun)

v1.22.5

[autoscaler]

🐛 Bug Fixes

• [USER] Autoscaler would not scale-down if the node-grp(i.e. machineDeployment) is under rolling update. (gardener/autoscaler#208, @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#202, @himanshu-kun)