-
Notifications
You must be signed in to change notification settings - Fork 119
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
k8s-1.30: Upgrade crio to v1.30 #1186
Conversation
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 Signed-off-by: Brian Carey <bcarey@redhat.com>
Skipping CI for Draft Pull Request. |
/test check-provision-k8s-1.30 |
/test check-provision-k8s-1.30 |
/cc @dhiller |
@brianmcarey: The following test failed, say
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. I understand the commands that are listed here. |
@brianmcarey can you remind me whether we have fixed the cri-o mirroring? |
The mirroring has been fixed here - kubevirt/project-infra#3391 |
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.
/approve
Thank you @brianmcarey ! 🎉
[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:
Approvers can indicate their approval by writing |
[486ee95 k8s-1.30: Upgrade crio to v1.30](kubevirt/kubevirtci#1186) [1d0a7b0 cluster-up: Update default provider to k8s-1.30](kubevirt/kubevirtci#1188) [be51633 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1187) [0a1b3b6 Run bazel run //robots/cmd/kubevirtci-bumper:kubevirtci-bumper -- -ensure-only-latest-three --k8s-provider-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-provision/k8s --cluster-up-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-up/cluster](kubevirt/kubevirtci#1142) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[486ee95 k8s-1.30: Upgrade crio to v1.30](kubevirt/kubevirtci#1186) [1d0a7b0 cluster-up: Update default provider to k8s-1.30](kubevirt/kubevirtci#1188) [be51633 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1187) [0a1b3b6 Run bazel run //robots/cmd/kubevirtci-bumper:kubevirtci-bumper -- -ensure-only-latest-three --k8s-provider-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-provision/k8s --cluster-up-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-up/cluster](kubevirt/kubevirtci#1142) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[486ee95 k8s-1.30: Upgrade crio to v1.30](kubevirt/kubevirtci#1186) [1d0a7b0 cluster-up: Update default provider to k8s-1.30](kubevirt/kubevirtci#1188) [be51633 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1187) [0a1b3b6 Run bazel run //robots/cmd/kubevirtci-bumper:kubevirtci-bumper -- -ensure-only-latest-three --k8s-provider-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-provision/k8s --cluster-up-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-up/cluster](kubevirt/kubevirtci#1142) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
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.
Release note: