Proposed title of this feature request

Supporting metallb as API/ingress endpoints

What is the nature and description of the request?

An alternative method to implementing https://issues.redhat.com/browse/RFE-3213 is if we could use the metallb + bgp option for our api loadbalancing that would be also a solution for us but unfortunately that is not possible because:

"MetalLB, which was added with support for layer 2 mode in OpenShift 4.9 and layer 3/BGP mode in OpenShift 4.10, provides a way for applications deployed to OpenShift to request a Service with type LoadBalancer. This is useful for applications you want to expose to clients on ports other than 80 and 443. For example, this could be a MariaDB database using port 3306 or an application spanning OpenShift and external resources which is using custom ports for communication."

While this is a very useful, and powerful capability, MetalLB cannot be used to replace either the ingress or API endpoints. MetalLB is a feature deployed after cluster deployment and not available early enough for the API, which needs to be accessible before other features and functions are deployed and configured, or default ingress domain." (source: https://cloud.redhat.com/blog/using-integrated-load-balancing-with-on-premises-openshift-4-ipi)

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

The customer is trying to use IPI installation but they have specific environment requirements that need to be supported by Openshift, we are trying to find ways to help the customer get these functions into OCP. We are trying to get them to move away from UPI installs and to use IPI (especially with Baremetal) but there are still some use cases like this and https://issues.redhat.com/browse/RFE-3213 which are not helping this customer.
List any affected packages or components.