Skip to content

Releases: kubernetes/autoscaler

cluster-autoscaler-chart-9.39.1

24 Sep 09:14
5e1d752
Compare
Choose a tag to compare

Scales Kubernetes worker nodes within autoscaling groups.

cluster-autoscaler-chart-9.39.0

23 Sep 22:44
a98d199
Compare
Choose a tag to compare

Scales Kubernetes worker nodes within autoscaling groups.

cluster-autoscaler-chart-9.38.0

23 Sep 14:08
fe6a1d6
Compare
Choose a tag to compare

Scales Kubernetes worker nodes within autoscaling groups.

Cluster Autoscaler 1.31.0

28 Aug 16:04
8bda275
Compare
Choose a tag to compare

Changelog

General

  • Cluster Autoscaler can now provision nodes before all pending pods are created and marked as unschedulable by scheduler. This behavior is disabled by default and can be enabled with --enable-proactive-scaleup flag. --pod-injection-limit flag is introduced to allow fine-tuning this behavior. (#7145)
    • This functionality can significantly speed up provisioning of nodes when hundreds or thousands of pods are created at the same time as well as lead to better scale-up decisions in those cases.
    • Injecting too many pods can make CA unstable, depending on number of NodeGroups and scalability of particular cloud provider integration. --pod-injection-limit can help control this.
  • Added support for ProvisioningRequest v1 API. (#7195)
  • Allows the user to use in-cluster kubernetes configuration while self-hosting cluster-autoscaler as a pod within their cluster. (#7156)
  • Faster handling of failed scale ups, useful especially with multiple quota or stockout errors across the cluster. (#7087)
  • Bin packing will be cut short after exceeding "maxBinpackingDuration". The "maxBinpackingDuration" is set using an new flag "--max-binpacking-time". This can prevent rare cases where CA gets unresponsive in scenarios with a very large number of pods pending. (#6556)
  • Added a new least-nodes expander (#6792)

AWS

  • Fix an issue in the Kubernetes Cluster Autoscaler where actual AWS instances could be incorrectly scaled down instead of placeholders. (#6911)
  • Fix an issue with reading taints on Managed Node Groups scaled to zero, that can cause scale-up of nodes with taints that pending pods don't tolerate (#6482)

Azure

  • ACTION REQUIRED: VMSS GPU Nodes must now also include the kubernetes.azure.com/accelerator label in addition to accelerator. (#7203)
  • From now on, users should refer to https://cloud-provider-azure.sigs.k8s.io/install/configs/ for configuration interface (#6947)
  • Fixed an issue where environment variables were not being passed in when config file exists (#6947)
  • Fixed an issue where some cloud provider configurations were not being validated when UseManagedIdentityExtension is set to true (#6947)
  • Renamed several fields from config file, with old names are still acceptable and taking precedence: useWorkloadIdentityExtension to useFederatedWorkloadIdentityExtension, vmssCacheTTL to vmssCacheTTLInSeconds, vmssVmsCacheTTL to vmssVirtualMachinesCacheTTLInSeconds, enableVmssFlex to enableVmssFlexNodes (#6947)
  • Renamed several environment variables, with old names are still acceptable and taking precedence: ARM_USE_MANAGED_IDENTITY_EXTENSION to ARM_USE_FEDERATED_WORKLOAD_IDENTITY_EXTENSION, AZURE_VMSS_CACHE_TTL to AZURE_VMSS_CACHE_TTL_IN_SECONDS, AZURE_VMSS_VMS_CACHE_TTL to AZURE_VMSS_VMS_CACHE_TTL_IN_SECONDS, AZURE_ENABLE_VMSS_FLEX to AZURE_ENABLE_VMSS_FLEX_NODES (#6947)
  • Fix some cases where instance cache is outdated but not getting refreshes (#7116)
  • Support cloud provider AAD certificate authentication (#7003)
  • getVMSS api will be called when using spot instances for having better updated information (#6470)
  • The AZURE_CLUSTER_AUTOSCALER_USER_AGENT_SUFFIX variable can be used to customize the user agent for the Azure provider of cluster-autoscaler. Setting this to -my-user-agent results in a user agent like Go/go1.22.5 (amd64-linux) go-autorest/v14.2.1 cluster-autoscaler-my-user-agent/v1.31.0-alpha.2. (#7033)
  • You can now optionally specify a default min and max size for Azure VMSSs through the auto discovery tags. Explicit min and max tags on VMSSs will still be given priority over the default. (#6863).
  • Skips Azure-specific node labels that might mistakenly categorize nodegroups as different when, in reality, they are similar. (#6634)

Cluster API

  • Added configurable autoscaling options to clusterapi provider allowing users to configure e.g. --scale-down-unneeded-time on a per node group level. (#6743)

GCE

  • GCE cloud provider will use Instance.List api to list mig instances. IGM.ListManagedInstances api will be used as a fall back mechanism and for listing instances for migs that have instances in creating or deleting states. This should improve performance in clusters with a large number of NodeGroups. (#6955)

Hetzner

  • Fixed exhausted node groups not backing off for Hetzner Provider (#6750)

Images

  • registry.k8s.io/autoscaling/cluster-autoscaler:v1.31.0
  • registry.k8s.io/autoscaling/cluster-autoscaler-arm64:v1.31.0
  • registry.k8s.io/autoscaling/cluster-autoscaler-amd64:v1.31.0
  • registry.k8s.io/autoscaling/cluster-autoscaler-s390x:v1.31.0

Full Changelog: cluster-autoscaler-1.30.0...cluster-autoscaler-1.31.0

vertical-pod-autoscaler-1.2.1

20 Aug 17:22
6569b77
Compare
Choose a tag to compare

What's changed:

#7169 - Prevent nil pointer dereference in vpa-recommender.

vertical-pod-autoscaler-1.2.0...vertical-pod-autoscaler-1.2.1

vertical-pod-autoscaler-1.2.0

08 Aug 14:14
Compare
Choose a tag to compare

What's Changed

Full Changelog: vertical-pod-autoscaler-1.1.2...vertical-pod-autoscaler-1.2.0

cluster-autoscaler-1.30.2

18 Jul 11:54
a0fce3c
Compare
Choose a tag to compare

Changelog

General

AWS

Hetzner

  • Backport #6750 [CA] fix(hetzner): missing error return in scale up/down into CA 1.30 by @Shubham82 in #7023

Images

  • registry.k8s.io/autoscaling/cluster-autoscaler:v1.30.2
  • registry.k8s.io/autoscaling/cluster-autoscaler-arm64:v1.30.2
  • registry.k8s.io/autoscaling/cluster-autoscaler-amd64:v1.30.2
  • registry.k8s.io/autoscaling/cluster-autoscaler-s390x:v1.30.2

Full Changelog: cluster-autoscaler-1.30.1...cluster-autoscaler-1.30.2

cluster-autoscaler-1.29.4

18 Jul 11:46
043b0c1
Compare
Choose a tag to compare

Changelog

General

  • Update vendor to use k8s 1.29.6 by @x13n in #7048
  • Backport #6528 [CA] Fix expectedToRegister to respect instances with nil status into CA1.29 by @Shubham82 in #6893

AWS

Azure

Hetzner

  • Backport #6750 [CA] fix(hetzner): missing error return in scale up/down into CA 1.29 by @Shubham82 in #7022

Images

  • registry.k8s.io/autoscaling/cluster-autoscaler:v1.29.4
  • registry.k8s.io/autoscaling/cluster-autoscaler-arm64:v1.29.4
  • registry.k8s.io/autoscaling/cluster-autoscaler-amd64:v1.29.4
  • registry.k8s.io/autoscaling/cluster-autoscaler-s390x:v1.29.4

Full Changelog: cluster-autoscaler-1.29.3...cluster-autoscaler-1.29.4

cluster-autoscaler-1.28.6

18 Jul 11:41
daeb681
Compare
Choose a tag to compare

Changelog

General

  • Update vendor to use k8s 1.28.11 by @x13n in #7049
  • Backport #6528 [CA] Fix expectedToRegister to respect instances with nil status into CA1.28 by @Shubham82 in #6892

AWS

Hetzner

  • Backport #6750 [CA] fix(hetzner): missing error return in scale up/down into CA 1.28 by @Shubham82 in #7021

Images

  • registry.k8s.io/autoscaling/cluster-autoscaler:v1.28.6
  • registry.k8s.io/autoscaling/cluster-autoscaler-arm64:v1.28.6
  • registry.k8s.io/autoscaling/cluster-autoscaler-amd64:v1.28.6
  • registry.k8s.io/autoscaling/cluster-autoscaler-s390x:v1.28.6

Full Changelog: cluster-autoscaler-1.28.5...cluster-autoscaler-1.28.6

addon-resizer-1.8.22

19 Jun 15:59
f36bbcd
Compare
Choose a tag to compare

What's Changed

  • Various dependency bumps
  • Added a Prometheus endpoint for monitoring to addon-resizer by @raywainman in #6916

Full Changelog: addon-resizer-1.8.21...addon-resizer-1.8.22