nginx-ingress: bump to 1.0.0 to support kube 1.22

[cristicalin]

What type of PR is this?

/kind bug

What this PR does / why we need it:
The nginx ingress controller stopped working with Kubernetes 1.22 with the deprecation of the v1beta1 and move to the stable API networking.k8s.io. Subsequently a new version of the nginx-ingress controller was released (https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.0.0) that supports the stable API down to kubernetes 1.19.
This PR moves our nginx-ingress controller to 1.0.0 to support all versions of kubernetes currently supported in kubespray master branch.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Ingress-nginx: upgrade to 1.0.0 with stable ingress API, this version requires explicitly setting `kubernetes.io/ingress.class: nginx` on managed ingresses

[k8s-ci-robot]

Hi @cristicalin. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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/test-infra repository.

[floryut]

@cristicalin You're on fire man, thanks a lot
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cristicalin, floryut

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:

• OWNERS [floryut]

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

[champtar]

/lgtm

[cloud-66]

@cristicalin Should we mention somewhere that nginx-ingress 1.0 has a breaking change? Someone , during upgrade cluster with master branch of kubespray, might think: "I upgrade cluster just to kubernetes v1.21 which still support networking.k8s.io/v1beta object " . And it will break the cluster, because nginx-ingress 1.0 does not support networking.k8s.io/v1beta .

[floryut]

I'll keep that in mind for the release note

[cristicalin]

We could also add differentiated version support and use a slightly older version for kubernetes < 1.22 like 1.0.0alpha2 which maintains the old API so we don’t break the expectations for default installs that don’t deliberately move to 1.22. We can drop the old version support when we tag kubespray 2.17 and bump the default kube_version.

…

________________________________ From: Florian Ruynat ***@***.***> Sent: Wednesday, September 8, 2021 10:34:47 AM To: kubernetes-sigs/kubespray ***@***.***> Cc: Cristian Calin ***@***.***>; Mention ***@***.***> Subject: Re: [kubernetes-sigs/kubespray] nginx-ingress: bump to 1.0.0 to support kube 1.22 (#7942) I'll keep that in mind for the release note — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fkubernetes-sigs%2Fkubespray%2Fpull%2F7942%23issuecomment-914994145&data=04%7C01%7C%7Cff4a85417b6440161f2008d9729b22c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637666832890143502%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2FXsO3IEJfCHRq7SjfZZ1ulN4nx%2FOFciYbzWaLi8qtxc%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fnotifications%2Funsubscribe-auth%2FABSSBNKEIQQ3EOAWGSV2RD3UA4GZPANCNFSM5DNXUBFQ&data=04%7C01%7C%7Cff4a85417b6440161f2008d9729b22c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637666832890153459%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YJiYCvbkR0nviCJwjZ4OpAjI0GimE%2B8alyG0QEtg1Fo%3D&reserved=0>. Triage notifications on the go with GitHub Mobile for iOS<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7Cff4a85417b6440161f2008d9729b22c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637666832890153459%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZqYiEJDtdtxMrWzw8T%2Bq0hqhNmgCND%2FWEeTcrqCo4dY%3D&reserved=0> or Android<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7Cff4a85417b6440161f2008d9729b22c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637666832890163414%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JadIeKwu20%2B%2FY2XB6OykaxLF6BvB7bTZcS8A4K%2FOlGQ%3D&reserved=0>.