Update ingress from v1beta1 to v1

[juniorjbn]

Update ingress from v1bet1 to v1 and update Ingress.spec.rules[0].http.paths[0].backend changes.
https://kubernetes.io/docs/concepts/services-networking/ingress/

[k8s-ci-robot]

Hi @juniorjbn. 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.

[aojea]

we discussed this some time ago, the problem is that this we are always going to break someone
ingress/v1 is 1.19 IIRC, it won't work for previous versions
ingress/v1beta1 will stop to work since 1.22 🤷

[BenTheElder]

ingress/v1 is 1.19 IIRC, it won't work for previous versions
ingress/v1beta1 will stop to work since 1.22 🤷

with 1.22 coming it might be time to switch though, we can add a note about this to the docs.
older releases have to eventually be best effort I think.

[aojea]

we enter here on the compatiblity problem, some ingresses need
ImplementationSpecific

[aojea]

I can't say which is better though

[BenTheElder]

we don't have to support all ingresses here, I'd prefer to use ingresses that can use portable upstream specs for the purposes of kind anyhow.

[aojea]

I can't say which pathType is more portabl XD

[rikatz]

Prefix is more portable :)

With Fixed you have all the traffic directed to a specific path only catched :)

[aojea]

with 1.22 coming it might be time to switch though, we can add a note about this to the docs.
older releases have to eventually be best effort I think.

this is going to be a drama XD, it took me a week to update k/k to v1,
but this is clear the way
/ok-to-test
@juniorjbn we don't have CI , have you tried it with at least one of the ingresses of the docs?

[aojea]

cc @rikatz

[aojea]

at least nginx ingress is not going to work kubernetes/ingress-nginx#7145

[rikatz]

Wanna release a beta next week :)

[BenTheElder]

Ingress Impl can't support both for some time?

[aojea]

/hold
until we have some positive feedback that the examples work

[aojea]

related kubernetes/ingress-nginx#7305 , right now the examples doesn't work for nginx

[BenTheElder]

I think we should probably roll forward with this, people are confused about the ingress-nginx failures and kind is nominally shipping v1.21, with 1.19+ having v1 AIUI. Yes some users are still on <= v1.18, but, similarly we cannot patch bugs in Kubernetes for those versions anymore, the last patch release is done upstream since we first started talking about this issue.

[BenTheElder]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, juniorjbn

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 [BenTheElder]

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

[aojea]

/hold cancel

[BenTheElder]

bypassing github actions flakes.