1. Proposed title of this feature request
  Allow customers to use their own LB for external api/ingress traffic for OCP 4 IPI VMware installs.

2. What is the nature and description of the request? 

  Allow customers to use their own LB for external api/ingress traffic for OCP 4 IPI VMware installs. This would be the exact same method that is approved for OpenStack and Baremental [1] [2].

  [1] https://docs.openshift.com/container-platform/4.8/installing/installing_bare_metal_ipi/ipi-install-post-installation-configuration.html#nw-osp-configuring-external-load-balancer_ipi-install-post-installation-configuration

  [2] https://docs.openshift.com/container-platform/4.8/networking/load-balancing-openstack.html#nw-osp-configuring-external-load-balancer_load-balancing-openstack

3. Why does the customer need this? (List the business requirements here)

  Customers who are not satisfied with the self-hosted LB architecture limitations ( traffic goes through a single node, node failover can cause traffic hit) can use their own LB.

4. List any affected packages or components.
  API
  Ingress
  LB