openshift / openshift-docs

OpenShift 3 and 4 product and community documentation
https://docs.openshift.com
Apache License 2.0
764 stars 1.76k forks source link

[enterprise-4.8] Issue in file release_notes/ocp-4-8-release-notes.adoc #34933

Closed amelie1979 closed 2 years ago

amelie1979 commented 3 years ago

Which section(s) is the issue in?

https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.html#ocp-4-8-networking-external-load-balancer

What needs fixing?

In OpenShift Container Platform 4.8, you can configure an external load balancer to handle apiVIP and ingressVIP traffic to the control plane of installer-provisioned clusters

Its not all installer-provisioned that is supporting this. (VMware vSphere has no instruction to do so). Looks like related only to OSP and Baremetal Installer-provisioned only.

jboxman commented 3 years ago

Refs https://github.com/openshift/openshift-docs/pull/33781.

jboxman commented 3 years ago

@johnwilkins, any thoughts on this? Thanks!

tradej commented 3 years ago

This is likely related to https://issues.redhat.com/browse/TELCODOCS-216, @johnwilkins is the correct contact.

johnwilkins commented 3 years ago

I can add a comment regarding VMWare, but I haven't worked on anything but installer-provisioned infrastructure and single node OpenShift. So it's not clear to me where else it would apply. Please advise on the other scenario(s), and I can add additional scenarios as needed.

On Wed, Jul 28, 2021 at 11:58 PM Tomas Radej @.***> wrote:

This is likely related to https://issues.redhat.com/browse/TELCODOCS-216, @johnwilkins https://github.com/johnwilkins is the correct contact.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openshift/openshift-docs/issues/34933#issuecomment-888853938, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALVRMOVRNC5ZEJACQSX5PLT2D3X7ANCNFSM5BES6YZA .

-- John Wilkins Red Hat @.*** (415) 425-9599 http://redhat.com

vikram-redhat commented 3 years ago

This is not applicable on OSP as support for it is only arriving in 4.9. https://issues.redhat.com/browse/OSASINFRA-2412. We should make sure QE acks the release notes adding these statements in.

actOnNow commented 3 years ago

OSP supports custom external LB since OCP 4.7 but not automated with IPI installer What OSP supports since OSP 4.7 is documentation for how to hook up your own external load balancer up to serve the api or openshift apps manually as a day 2 operation. What is is planned in OCP 4.9 with https://issues.redhat.com/browse/OSASINFRA-2412 is support for using kubernetes load balancer services to automatically expose openshift applications outside of your cluster with OSP octavia LB using IPI installer as a Day-1 operation

openshift-bot commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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[bot] commented 2 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-docs/issues/34933#issuecomment-1012300870): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.