v1.20.1

[autoscaler]

🏃 Others

• [USER] Gardener autoscaler now in sync with upstream v1.20.3 (gardener/autoscaler#130, @himanshu-kun)

v1.22.0

[autoscaler]

🏃 Others

• [DEVELOPER] IT retry to scale up and down the pod in case on conflicts. Retry of 5 times with interval of 10 millisecond is kept (gardener/autoscaler#124, @Mkmittal)

📰 Noteworthy

• [USER] sync the changes till v1.22.0 of upstream autoscaler (gardener/autoscaler#121, @himanshu-kun)

v1.21.0

[autoscaler]

🏃 Others

• [USER] NodeTemplate is not formed using cache in case nodegrp has minimum size zero. This is done to keep nodeTemplate updated even when instance type of nodegrp is updated. (gardener/autoscaler#119, @himanshu-kun)
• [OPERATOR] CA is now synced with upstream v1.21.0 (gardener/autoscaler#116, @himanshu-kun)

v1.20.0

[autoscaler]

🏃 Others

• [USER] CA now balances between similar node groups properly during scale-from-zero. (gardener/autoscaler#114, @himanshu-kun)
• [DEVELOPER] Gardener CA now supports basic IT to run locally. (gardener/autoscaler#111, @AxiomSamarth)

v0.19.0

[autoscaler]

🏃 Others

• [USER] Gardener Autoscaler now supports generic scale from zero. Traditionally, nodes are scaled by Autoscaler by generating node template for a new node that would accomodate the pending pods. This node template is generated either by referring to the node spec of the already existing node in the nodeGroup or by referring to the cloud provider specific catalogue which provides the node details like cpu, gpu, memory, region, zone, instanceType etc. The latter scenario is the scale from zero scenario where there are zero nodes in the nodeGroup that is expected to scale up and so far the existing logic limited this feature to AWS and Azure only. (gardener/autoscaler#102, @AxiomSamarth)
  • Now, with the introduction of nodeTemplate property in the MachineClass, the scale from zero feature has been extended generically across all providers.

v0.18.0

[autoscaler]

🏃 Others

• [OPERATOR] Added support for m6i type AWS machine types (#97, @patrickhuy)

v0.10.2

[autoscaler]

🐛 Bug Fixes

• [USER] Avoids panics when VM type isn't found during scale from zero (#81, @ialidzhikov)
• [USER] Fetches the VM from the correct map for MCM provider Azure and hence doesn't panic anymore (#81, @ialidzhikov)

v0.17.0

[autoscaler]

🐛 Bug Fixes

• [DEVELOPER] Avoids panics when VM type isn't found during scale from zero (#77, @prashanth26)
• [DEVELOPER] Fetches the VM from the correct map for MCM provider Azure and hence doesn't panic anymore (#77, @prashanth26)

🏃 Others

• [USER] Added support for 12 new AWS instance types and 1 new Azure Instance Types (#85, @AxiomSamarth)
• [USER] Do not return errors while fetching details for an unmanaged node. (#79, @jsravn)

v0.16.2

[autoscaler]

🏃 Others

• [USER] Added support for 12 new AWS instance types and 1 Azure instance type while scaling up from zero. (#86, @AxiomSamarth)

v0.16.1

[autoscaler]

🐛 Bug Fixes

• [DEVELOPER] Avoids panics when VM type isn't found during scale from zero (#78, @prashanth26)
• [DEVELOPER] Fetches the VM from the correct map for MCM provider Azure and hence doesn't panic anymore (#78, @prashanth26)