-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
set minimum minikube legacy version to v1.26.0 for containerd cri #17220
set minimum minikube legacy version to v1.26.0 for containerd cri #17220
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: prezha 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 |
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube ingress: 27.1s 28.0s 27.5s 27.2s 27.6s Times for minikube (PR 17220) start: 49.8s 50.0s 50.6s 50.3s 51.8s docker driver with docker runtime
Times for minikube (PR 17220) start: 21.5s 22.4s 24.6s 21.7s 24.5s Times for minikube (PR 17220) ingress: 20.9s 22.9s 20.8s 20.8s 19.8s docker driver with containerd runtime
Times for minikube ingress: 32.4s 31.3s 31.4s 30.3s 31.3s Times for minikube start: 24.1s 22.6s 23.6s 24.5s 24.2s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
That configuration is from docker, not from containerd. We need something that removes it (or more like : doesn't disable it), when using containerd |
fixes #17219
solution is to use at least minikube v1.26.0 for this test to be able to pass
details:
v1.25.2 (and earlier versions)
note:
unknown service runtime.v1alpha2.RuntimeService
error indicates that the cri is disabled, and, indeed, there'sdisabled_plugins = ["cri"]
from default containerd's config:and so, we cannot generateContainerdConfig(), which then leaves default containerd intact, following with expected failure with the above error
v1.26.0+
here, thanks to how the kicbase was built (via Dockerfile), we have expected containerd config (patched to our needs):
note: i was thinking about making minikube more resilient to this and support older versions by changing our code to supply our initial containerd config if we see that the default one is present instead, but since we change which containerd version and then also change the initial config (format & values) we supply over time, that's not a viable option