-
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
Addon ingress: Update ingress-nginx/controller image from v1.9.0 to v1.9.1 #17348
Addon ingress: Update ingress-nginx/controller image from v1.9.0 to v1.9.1 #17348
Conversation
Hi @minikube-bot. 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. |
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 52.5s 53.5s 50.5s 51.4s 49.4s Times for minikube ingress: 27.8s 28.2s 25.3s 28.6s 28.2s docker driver with docker runtime
Times for minikube start: 25.7s 25.3s 22.1s 25.3s 25.6s Times for minikube ingress: 22.9s 20.9s 20.9s 20.8s 20.9s docker driver with containerd runtime
Times for minikube start: 20.7s 23.8s 23.1s 23.7s 21.8s Times for minikube ingress: 19.4s 32.4s 31.4s 47.3s 31.4s |
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: minikube-bot, 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 |
The ingress-nginx project released a new version
This PR was auto-generated by
make update-ingress-version
using update-ingress-version.yml CI Workflow.