Addon ingress: Update ingress-nginx/controller image from v1.11.3 to v1.12.2

[minikube-bot]

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.

[k8s-ci-robot]

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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-sigs/prow repository.

[khumps]

There is a CVE patched by 1.12.1

#20578

[minikube-pr-bot]

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment	Test Name	Flake Rate
Docker_Windows (2 failed)	TestErrorSpam/setup(gopogh)	Unknown
Docker_Windows (2 failed)	TestStartStop/group/old-k8s-version/serial/SecondStart(gopogh)	Unknown
Docker_Linux_crio (2 failed)	TestFunctional/parallel/ImageCommands/ImageListShort(gopogh)	0.00% (chart)

Besides the following environments also have failed tests:

• KVM_Linux_crio: 12 failed (gopogh)

• Docker_Cloud_Shell: 3 failed (gopogh)

• Docker_Linux_crio_arm64: 1 failed (gopogh)

• Hyper-V_Windows: 12 failed (gopogh)

To see the flake rates of all tests by environment, click here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: minikube-bot
Once this PR has been reviewed and has the lgtm label, please assign spowelljr for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 20201) |
+----------------+----------+---------------------+
| minikube start | 53.3s    | 55.1s               |
| enable ingress | 18.6s    | 16.8s               |
+----------------+----------+---------------------+

Times for minikube start: 52.2s 52.5s 54.2s 54.4s 53.2s
Times for minikube (PR 20201) start: 55.8s 57.4s 51.6s 55.4s 55.1s

Times for minikube ingress: 18.6s 16.3s 19.2s 19.7s 19.2s
Times for minikube (PR 20201) ingress: 16.2s 15.7s 15.7s 16.1s 20.2s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 20201) |
+----------------+----------+---------------------+
| minikube start | 24.5s    | 24.8s               |
| enable ingress | 12.8s    | 13.1s               |
+----------------+----------+---------------------+

Times for minikube start: 24.3s 24.5s 25.4s 24.2s 23.9s
Times for minikube (PR 20201) start: 24.6s 23.7s 24.2s 24.0s 27.4s

Times for minikube ingress: 12.4s 12.8s 12.9s 13.4s 12.4s
Times for minikube (PR 20201) ingress: 12.4s 12.4s 13.3s 13.8s 13.3s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 20201) |
+----------------+----------+---------------------+
| minikube start | 25.2s    | 23.4s               |
| enable ingress | 23.1s    | 25.3s               |
+----------------+----------+---------------------+

Times for minikube start: 25.6s 23.5s 26.1s 24.5s 26.1s
Times for minikube (PR 20201) start: 22.7s 21.8s 22.9s 24.7s 24.8s

Times for minikube ingress: 22.9s 22.9s 22.8s 23.9s 22.9s
Times for minikube (PR 20201) ingress: 27.8s 22.9s 22.9s 29.8s 22.9s

[medyagh]

clean up duplicates

[andrewspiers]

Hi @medyagh is there a PR that duplicates this one? I see the linked issue #20578 still open, and I think the original reason, a security issue in versions of ingress, is still valid. See for example
https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/critical-vulnerabilities-ingress-nginx-controller-kubernetes