cluster-autoscaler-1.35.1

Changes by Kind

Feature

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

Bug or Regression

• Fixed overwriting CapacityBuffer conditions and fixed typos in condition messages and reasons (#9252, @jackfrancis)
• huawei-cloud-provider: Nodes without providerId are skipped (with a warning), and CA continues to work normally for other nodes. (#9208, @Hargeek)

Other (Cleanup or Flake)

• Update Kubernetes dependencies to v1.35.6 (#9858, @jackfrancis)

Uncategorized

• Azure: implement AtomicIncreaseSize for VMS (#9796, @reneeli123)
• Azure: optional ETag optimistic concurrency on VMSS capacity updates (#9838, @mboersma)
• Do not override condition in buffers limits translator (#9309, @norbertcyran)
• Fixed CAPI provider failing to initialize when using CAPI v1.11+ with infrastructure providers that only serve v1beta1 APIs (e.g. Azure CAPZ). (#9755, @LiangquanLi930)
• Fixed a bug with DRA node readiness processor not considering devices from multiple resource slices (#9460, @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. (#9553, @tallaxes)
• Regenerate Azure static SKU list (#9373, @rrangith)

Images

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