"Configuring an external load balancer" Section contains potentially inaccurate/incomplete information.

This page and several others include the following adoc file for this content:
modules/nw-osp-configuring-external-load-balancer.adoc

Given that the filename includes OSP, I'm assuming this content was originally written for OpenShift on OpenStack, and then not updated with VMWare/vSphere content when it was included in the VMWare pages.

There are _three_ main issues with this content:

1.  In the below quote from the pre-requisites setting.  This does not make sense in VMWare environments.  There is no concept of floating IPs and in most cases external load balancers are not located on the same subnet.  

I would advise augmenting this section to include adding a sub-bullet around having traffic be routable between the external LB and the OCP nodes.

"""
* Your load balancer must be able to access every machine in your cluster. Methods to allow this access include:
** Attaching the load balancer to the cluster's machine subnet.
** Attaching floating IP addresses to machines that use the load balancer.
"""

2.  The below quoted section is confusing:

"""
[IMPORTANT]
====
External load balancing services and the control plane nodes must run on the same L2 network, and on the same VLAN when using VLANs to route traffic between the load balancing services and the control plane nodes.
====
"""

For starters, it's unclear which endpoints this applies to.  References to control plane nodes are ambiguous.  Does this mean the API endpoint?

Second "VLANs to route traffic".  VLANs don't route traffic.  VLANs are L2.  Routing is a L3 function, not a L2 concept.  

Also, it's _highly unusual_ to require L2 adjacency between an External Loadbalancer and the backend pool.  I know this is technically not required because it's not required in a UPI installation.  

As written, my customers are not sure what this even means!


3.  This document does not reference our recommendations around Ingress Controller health checks:

https://access.redhat.com/solutions/4677531

Health checks are essential to ensuring that the external load balancer works as expected.  These should be included in the document.

1.
2.
3.