-
Notifications
You must be signed in to change notification settings - Fork 284
🌱 Bump e2e to use k8s v1.34.2 #2836
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
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/test pull-cluster-api-provider-openstack-e2e-full-test |
|
Ok so there is the downside of using a kind cluster for clusterctl upgrade. We need to make sure we have a node image with the correct version for it. |
7066450 to
cc1c460
Compare
|
/test pull-cluster-api-provider-openstack-e2e-full-test |
Since we use kind for the clusterctl upgrade tests, we need to use a kubernetes version that has a kind node image available also. I have added a separate variable for this. (We could also build the kind image but that takes time and resources.) Signed-off-by: Lennart Jern <[email protected]>
cc1c460 to
b004100
Compare
|
/test pull-cluster-api-provider-openstack-e2e-full-test |
|
Ok this works |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 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 |
smoshiur1237
left a comment
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
What this PR does / why we need it:
Run e2e tests with k8s v1.34.2. Upgrades from v1.33.1.
Also changes the image names to not include the versions. It felt a bit unnecessary to constantly change both the URLs and the names.
Since we use kind for the clusterctl upgrade tests, we need
to use a kubernetes version that has a kind node image available also.
I have added a separate variable for this.
(We could also build the kind image but that takes time and resources.)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs: