This is a patch release that enables addon-resizer to work with Kubernetes 1.37.

What's Changed

• Add support for apiserver_resource_objects metric by @liggitt in #10107

Full Changelog: addon-resizer-1.8.23...addon-resizer-1.8.24

Images

• registry.k8s.io/autoscaling/addon-resizer:1.8.24
• registry.k8s.io/autoscaling/addon-resizer-amd64:1.8.24
• registry.k8s.io/autoscaling/addon-resizer-arm:1.8.24
• registry.k8s.io/autoscaling/addon-resizer-arm64:1.8.24
• registry.k8s.io/autoscaling/addon-resizer-ppc64le:1.8.24
• registry.k8s.io/autoscaling/addon-resizer-s390x:1.8.24

Automatically adjust resources for your workloads

Changes by Kind

Regression

• Fixed the VPA recommender ignoring the --history-cpu-metric and --history-memory-metric flags when using the Prometheus history provider, which caused the historical queries to omit the configured metric name. (#9753, @ulascansenturk)
• Fixed VPA checkpoint loading to prevent recommendations from restarting from scratch (#10052, @adrianmoisey)

Bug

• Fix bug where VPA Checkpoint GC error message wasn't logging correctly (#9886, @adrianmoisey)
• Add reasons to in-place update deferred log messages (#9964, @omerap12)

Other (Cleanup or Flake)

• [vpa-release-1.7] Bump the actions group across 3 directories with 1 update by @k8s-infra-cherrypick-robot in #9735
• Bump the patch-updates group across 2 directories with 19 updates by @dependabot[bot] in #9776
• Bump the patch-updates group across 2 directories with 37 updates by @dependabot[bot] in #9938
• Bump the actions group across 3 directories with 1 update by @dependabot[bot] in #9979
• Bump the patch-updates group across 2 directories with 3 updates by @dependabot[bot] in #9982
• Bump to k8s 1.36.3 patch versions by @adrianmoisey in #10046
• Bump VPA to 1.7.1 by @adrianmoisey in #10053
• Bump to VPA 1.7.1 by @adrianmoisey in #10058

Full Changelog: vertical-pod-autoscaler-1.7.0...vertical-pod-autoscaler-1.7.1

Changes by Kind

Bug or Regression

• CA ProvisioningRequest: Apply Provisioned condition with SSA (#10017, @norbertcyran)
• Scaleway: report node in error as InstanceCreating so CA detects it faster (#10019, @Tomy2e)

Images

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

Changes by Kind

Bug or Regression

• Azure Cluster Autoscaler now handles VMSS target-size cache failures during delete operations more defensively, preventing negative cached sizes and target-size panics after failed or uncertain VMSS deletes. (#9881, @tallaxes)
• CA ProvisioningRequest: Apply Provisioned condition with SSA (#10026, @AaronLiChen)
• Scaleway: report node in error as InstanceCreating so CA detects it faster (#10018, @Tomy2e)
• Use application/json for ProvisioningRequest client config (#10016, @AaronLiChen)

Uncategorized

• Fix Azure provider incorrectly labeling ARM64 VM node templates as amd64 (#9381, @rrangith)

Images

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

Changes by Kind

Bug or Regression

• CA ProvisioningRequest: Apply Provisioned condition with SSA (#10025, @AaronLiChen)
• Scaleway: report node in error as InstanceCreating so CA detects it faster (#10021, @Tomy2e)
• Use application/json for ProvisioningRequest client config (#10015, @AaronLiChen)

Images

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

Changes by Kind

Bug or Regression

• CA ProvisioningRequest: Apply Provisioned condition with SSA (#10024, @AaronLiChen)
• Scaleway: report node in error as InstanceCreating so CA detects it faster (#10020, @Tomy2e)
• Use application/json for ProvisioningRequest client config (#10014, @AaronLiChen)

Images

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

Scales Kubernetes worker nodes within autoscaling groups.

Changes by Kind

Feature

• Azure: implement AtomicIncreaseSize for VMSS (#9764, @jackfrancis)

Bug or Regression

• Azure Cluster Autoscaler now handles VMSS target-size cache failures during delete operations more defensively, preventing negative cached sizes and target-size panics after failed or uncertain VMSS deletes. (#9880, @tallaxes)

Other (Cleanup or Flake)

• Update k8s deps to v1.34.9 (#9874, @jackfrancis)

Uncategorized

• Add template-node label to mitigate scale up issue (#9793, @NedAnd1)
• Azure: OperationPreempted does not retry if delete fails (#9834, @MaximilianoUribe)
• Azure: implement AtomicIncreaseSize for VMS (#9798, @reneeli123)
• Fix Azure provider incorrectly labeling ARM64 VM node templates as amd64 (#9380, @rrangith)
• Fix DraCustomResourcesProcessor ignoring devices located in different resource slices (#9463, @mtrqq)
• Pods with hard TopologySpreadConstraints using the default nodeTaintsPolicy will no longer cause scale-down/scale-up oscillation. The scale-down simulation now faithfully models the drain taint, matching real scheduler behavior. Pods using nodeTaintsPolicy: Honor are unaffected and continue to scale down correctly. (#9559, @tallaxes)
• Regenerate Azure static SKU list (#9372, @rrangith)

Images

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

Changes by Kind

Feature

• Azure: implement AtomicIncreaseSize for VMSS (#9789, @jackfrancis)

Bug or Regression

• Azure Cluster Autoscaler now handles VMSS target-size cache failures during delete operations more defensively, preventing negative cached sizes and target-size panics after failed or uncertain VMSS deletes. (#9879, @tallaxes)

Other (Cleanup or Flake)

• Update k8s deps to v1.33.13 (#9875, @jackfrancis)

Uncategorized

• Add template-node label to mitigate scale up issue (#9794, @NedAnd1)
• Azure: OperationPreempted does not retry if delete fails (#9835, @MaximilianoUribe)
• Azure: implement AtomicIncreaseSize for VMS (#9797, @reneeli123)
• Fix Azure provider incorrectly labeling ARM64 VM node templates as amd64 (#9379, @rrangith)
• Fix DraCustomResourcesProcessor ignoring devices located in different resource slices (#9464, @mtrqq)
• Fixed an issue where Exoscale instance pool node groups ignored the configured minimum size and defaulted to 1. (#9512, @Debasish-87)
• Pods with hard TopologySpreadConstraints using the default nodeTaintsPolicy will no longer cause scale-down/scale-up oscillation. The scale-down simulation now faithfully models the drain taint, matching real scheduler behavior. Pods using nodeTaintsPolicy: Honor are unaffected and continue to scale down correctly. (#9560, @tallaxes)
• Regenerate Azure static SKU list (#9371, @rrangith)

Images

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