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)

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 and min-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 existing failure-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)