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.4registry.k8s.io/autoscaling/cluster-autoscaler-arm64:v1.34.4registry.k8s.io/autoscaling/cluster-autoscaler-amd64:v1.34.4registry.k8s.io/autoscaling/cluster-autoscaler-s390x:v1.34.4