k8s-1.30: Upgrade crio to v1.30

brianmcarey commented 3 months ago

What this PR does / why we need it:

Kubernetes and cri-o versions should be aligned.

cri-o released v1.30.0[1] a number of days ago. Update the kubernetes v1.30 provider to use this new version

[1] https://github.com/cri-o/cri-o/releases/tag/v1.30.0

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:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

kubevirt-bot commented 3 months ago

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

brianmcarey commented 3 months ago

/test check-provision-k8s-1.30

brianmcarey commented 3 months ago

/test check-provision-k8s-1.30

brianmcarey commented 3 months ago

/cc @dhiller

kubevirt-bot commented 3 months ago

@brianmcarey: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
check-up-kind-1.27-vgpu	99fc020eb0e6f39e21daca357cc7f8a7a3ad290e	link	false	`/test check-up-kind-1.27-vgpu`

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

dhiller commented 3 months ago

@brianmcarey can you remind me whether we have fixed the cri-o mirroring?

brianmcarey commented 3 months ago

@brianmcarey can you remind me whether we have fixed the cri-o mirroring?

The mirroring has been fixed here - https://github.com/kubevirt/project-infra/pull/3391

kubevirt-bot commented 3 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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: - ~~[OWNERS](https://github.com/kubevirt/kubevirtci/blob/main/OWNERS)~~ [dhiller] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

kubevirt / kubevirtci

k8s-1.30: Upgrade crio to v1.30 #1186