-
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
Remove useless check of baremetal driver for ingress addon #12735
Conversation
Hi @zigarn. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Can one of the admins verify this patch? |
So this is a little more complex than it seems. The check itself is definitely in the wrong spot (a driver can't both be container-based and baremetal, clearly), but ingress is currently not working on baremetal at all, thus the reintroduction of the check, |
Works perfectly for us to use none driver and ingress addon. |
Good enough for me! /ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 49.7s 47.1s 45.6s 47.8s 48.9s Times for minikube ingress: 31.3s 30.8s 31.3s 31.8s 32.3s docker driver with docker runtime
Times for minikube start: 22.6s 21.4s 21.8s 22.2s 22.1s Times for minikube ingress: 34.4s 34.9s 34.9s 35.0s 27.5s docker driver with containerd runtime
Times for minikube start: 30.7s 43.9s 44.5s 43.8s 43.9s Times for minikube ingress: 43.4s 37.9s 32.9s 19.0s 32.4s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sharifelgamal, zigarn 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 |
Remove wrongly re-introduced (ee74d42, wrongly nested, so useless) check initially removed in #9577