Skip to content

✨ Bump autoscaler to a9cb59fdd #12643

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 28, 2025
Merged

✨ Bump autoscaler to a9cb59fdd #12643

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions test/e2e/data/autoscaler/autoscaler-to-workload-workload.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ spec:
app: cluster-autoscaler
spec:
containers:
- image: registry.k8s.io/autoscaling/cluster-autoscaler:${AUTOSCALER_VERSION}
- image: gcr.io/k8s-staging-autoscaling/cluster-autoscaler:v20250814-cluster-autoscaler-chart-9.50.1-4-ga9cb59fdd
name: cluster-autoscaler
command:
- /cluster-autoscaler
Expand All @@ -200,12 +200,6 @@ spec:
- --max-nodes-total=6
# Set the log verbosity
- --v=4
env:
# Per default autoscaler uses the preferred apiVersion to retrieve MachineDeployments.
# If that apiVersion is v1beta2 the current autoscaler implementation is not able
# to resolve infrastructureRefs as the ref format changed. This would break scale from zero.
- name: CAPI_VERSION
value: v1beta1
volumeMounts:
- name: kubeconfig-management-cluster
mountPath: /management-cluster
Expand Down