[v1] Example ingress YAML uses v1 but old serviceName/Port for backends

[maybe-sybr]

NGINX Ingress controller version: 1.0.0-beta.1

Kubernetes version (use kubectl version): Not relevant but 1.21+ server

What happened:
Found while attempting to work out if #7410 was actually a bug or my fault. I copied some example YAML from docs/user-guide/basic-usage.md and it appears to have been updated to use apiVersion: v1 but not the new backend YAML spec. It looks like #7362 needs to be ported onto the dev-v1 branch.

Anything else we need to know:

/kind documentation

[k8s-ci-robot]

@maybe-sybr: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[kundan2707]

/assign

[strongjz]

Any update @kundan2707 ? Do you have a PR open for this?

[strongjz]

I see, there is some confusion, I apologize, the examples in main are pre v1 updates. We are working on getting everything switched over for the ingress-nginx v1 update to support v1 ingress and k8s > 1.19.

We are tracking that here #7398

/close

[k8s-ci-robot]

@strongjz: Closing this issue.

In response to this:

I see, there is some confusion, I apologize, the examples in main are pre v1 updates. We are working on getting everything switched over for the ingress-nginx v1 update to support v1 ingress and k8s > 1.19.

We are tracking that here #7398

/close

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.