Azure scale: bump CAPZ to 1.21 #35893
Open
+1
−1
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.
The CAPZ release-1.20 branch is currently failing to build clusters for the ci-kubernetes-e2e-azure-scalability job since the removal of the kubelet's
--pod-infra-container-imageflag in kubernetes/kubernetes#133779, e.g. https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-azure-scalability/1986706943242145792.This PR bumps CAPZ to the release-1.21 branch which includes kubernetes-sigs/cluster-api-provider-azure#5961 to reference newer VM images built with kubernetes-sigs/image-builder#1866 that no longer set that flag.