The NOTE in https://docs.openshift.com/container-platform/4.14/virt/virtual_machines/virt-accessing-vm-ssh.html#using-services-ssh_virt-accessing-vm-ssh says that "... in layer 2 mode. The BGP mode is not supported.". That is not accurate. While we test integration with MetalLB only by utilizing its L2 mode (for simplicity of cluster setup), our support is not limited to that. The selected MetalLB mode in no way affects how MetalLB and CNV interact (in fact they do not interact at all, they have a layer of Kubernetes Services between them), so there is not reason to support one bot not the other. 

4.12+

Always

1. Go to https://docs.openshift.com/container-platform/4.14/virt/virtual_machines/virt-accessing-vm-ssh.html#using-services-ssh_virt-accessing-vm-ssh
2. Read the NOTE

For on-premise clusters, you can configure a load balancing service by 
using the MetalLB Operator in layer 2 mode. The BGP mode is not 
supported. The MetalLB Operator is installed in the metallb-system namespace.

For on-premise clusters, you can configure a load balancing service by 
using the MetalLB Operator. The MetalLB Operator is installed in the metallb-system namespace.