-
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
feat: check connectivity outside minikube once it fails #18859
Conversation
Can one of the admins verify this patch? |
please update the description with the new UI |
/ok-to-test |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Steven Powell <[email protected]>
Co-authored-by: Steven Powell <[email protected]>
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Steven Powell <[email protected]>
Co-authored-by: Steven Powell <[email protected]>
This comment has been minimized.
This comment has been minimized.
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
Co-authored-by: Steven Powell <[email protected]>
kvm2 driver with docker runtime
Times for minikube start: 46.7s 46.5s 48.4s 50.4s 48.2s Times for minikube ingress: 25.0s 22.9s 24.4s 26.9s 22.9s docker driver with docker runtime
Times for minikube ingress: 21.8s 21.8s 21.8s 23.3s 21.3s Times for minikube start: 24.1s 23.7s 21.8s 24.9s 24.6s docker driver with containerd runtime
Times for minikube start: 21.9s 20.8s 23.6s 19.5s 20.4s Times for minikube ingress: 32.3s 31.8s 47.8s 31.8s 31.8s |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ComradeProgrammer, 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 |
feat: check connectivity outside minikube once it fails
FIX #18754
After
This container is also having trouble accessing https://registry.k8s.io outside the minikube
is also printed on the console