[enterprise-4.6] Issue in file networking/routes/route-configuration.adoc

[saumeya]

Which section(s) is the issue in?

Openshift docs -> under Networking -> under Configuring routes (https://docs.openshift.com/container-platform/4.8/networking/routes/route-configuration.html#nw-ingress-creating-a-route-via-an-ingress_route-configuration)

The Ingress Yaml that is written contains fields like serviceName and servicePort which are no longer supported and result in error

What needs fixing?

Update the Yaml definition (there are 2 Yamls in the same section where this needs to be updated) to

backend:        
  service:
    name: frontend
    port:
      number: 443

[skrthomas]

@saumeya Hi, thanks for filing a docs issue! Can you point me to where you're seeing serviceName and servicePort are no longer supported? We just had a docs PR merged for this same yaml definition to change to serviceName and servicePort: https://github.com/openshift/openshift-docs/pull/41325/files, so I think the yaml should be corrected now in the link you pasted above.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.