-
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
recommend kindnet for multinode even for non-docker cr #11182
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: prezha The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -150,6 +141,15 @@ func chooseDefault(cc config.ClusterConfig) Manager { | |||
return KindNet{cc: cc} | |||
} | |||
|
|||
if cc.KubernetesConfig.ContainerRuntime != "docker" { |
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.
I am confused, is this just moving the code down ?
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.
@medyagh yes, that is correct - before, it would recommend 'bridge' for non-docker cr, even for multinode, and because of
minikube/pkg/minikube/cni/bridge.go
Line 85 in 8ce6326
return fmt.Errorf("bridge CNI is incompatible with multi-node clusters") |
this ensures that it first checks if it is multinode and if so - recommend kindnet
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 50.0s 46.4s 51.0s 50.8s 50.2s Times for minikube ingress: 33.8s 35.2s 34.3s 36.7s 42.3s docker driver with docker runtime
Times for minikube ingress: 29.5s 36.5s 31.5s 29.1s 35.0s Times for minikube start: 22.9s 20.9s 21.5s 22.5s 21.0s docker driver with containerd runtime
Times for minikube start: 30.8s 46.4s 43.2s 43.0s 47.1s |
i'll close this one in favour of #11209 |
@prezha: Closed this PR. 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. |
fixes #11181
fixes #10822
as seen in logs:
or