-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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.
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
CAPZ: fix kubernetes version in apiversion test #26755
CAPZ: fix kubernetes version in apiversion test #26755
Conversation
/assign @jackfrancis cc @mboersma |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon, jackfrancis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@CecileRobertMichon: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-azure#capz-periodic-apiversion-upgrade-main
The apiversion upgrade test attempts to create a test workload cluster from an "old" management cluster (created with capz v1alpha4). However, CAPZ v0.5.x does not support new Kubernetes versions due to the SKU naming change (kubernetes-sigs/cluster-api-provider-azure#2302).
Since CAPZ e2e tests were updated to use the latest version available in new image SKUs, this test broke as the older management cluster is unable to find the new images. This pins the test to the latest supported 1.22 version in v1alpha4.