-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Kicbase: Revert cri-o from v1.29 to v1.24 #18367
Conversation
ok-to-build-image |
Hi @spowelljr, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
/ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh, spowelljr 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 |
kvm2 driver with docker runtime
Times for minikube start: 49.7s 52.6s 52.5s 49.3s 51.7s Times for minikube ingress: 27.0s 25.6s 25.2s 23.1s 26.2s docker driver with docker runtime
Times for minikube start: 25.7s 23.3s 24.9s 26.3s 23.6s Times for minikube ingress: 23.3s 19.3s 20.3s 20.3s 20.3s docker driver with containerd runtime
Times for minikube start: 24.3s 23.9s 24.3s 24.0s 23.5s Times for minikube ingress: 30.8s 31.8s 30.8s 30.8s 46.8s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
As discussed during office hours and as evidenced in #18294, using newer crictl and cri-o versions results in incompatibility with previous Kubernetes versions. Rolling back until we implement a mechanism to use the matching cri-o and crictl versions to the chosen Kubernetes version (#18359).