Pin AWS CCM image tag for k8s 1.25 #13543
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the k8s 1.24 rc.0 published, our prow jobs that use k8s CI builds are now on k8s 1.25.
To avoid kubernetes/cloud-provider-aws#339 in the latest AWS CCM tag we have to pin 1.25 to the same tag as k8s 1.23 and 1.24
Should fix https://testgrid.k8s.io/kops-misc#kops-aws-misc-arm64-ci
you can see
latest
is being used in the daemonset here: https://storage.googleapis.com/kubernetes-jenkins/logs/e2e-kops-aws-misc-arm64-ci/1517088467119509504/artifacts/cluster-info/kube-system/daemonsets.yamland the panic is occurring: https://storage.googleapis.com/kubernetes-jenkins/logs/e2e-kops-aws-misc-arm64-ci/1517088467119509504/artifacts/cluster-info/kube-system/aws-cloud-controller-manager-kw82b/logs.txt