-
Notifications
You must be signed in to change notification settings - Fork 267
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
Increment versions of k8s used in CI #2278
Conversation
Wouldn't we have to switch to 1.24 just in a bit? |
b715c89
to
9c940e4
Compare
Well not sure when 1.24 becomes available in kubevirtci, also we can decide if that is something we want to do or not at any time. |
Gotcha, right This uncovered some related nils on looking up csidrivers: |
Yeah there seems to be a problem with kubevirt/kubevirtci#794 with some of the tests. |
@awels ceph bump merged in kubevirtci, would you like to bump it here or new PR? |
I was waiting for that to merge, going to bump it here |
Take advantage of newer versions of k8s for testing. Signed-off-by: Alexander Wels <awels@redhat.com>
Signed-off-by: Alexander Wels <awels@redhat.com>
9c940e4
to
6fe28cb
Compare
/test pull-containerized-data-importer-e2e-hpp-latest |
I'll double-check number of tests ran on ceph lane vs older version to make sure we're not skipping everything lol |
/test pull-containerized-data-importer-e2e-nfs |
Same exact amount of ceph tests as before |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awels 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 |
@awels should we cherry pick to 49? |
Yeah since we want 1.49 to support k8s 1.23 at a minimum. |
@awels: new pull request created: #2293 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. |
Signed-off-by: Alexander Wels awels@redhat.com
What this PR does / why we need it:
Instead of 1.21 and 1.22, now use 1.22 and 1.23
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:
Release note: