Hi,

I'm reporting an issue that slowed me down for half a day. While following the steps here:

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html-single/clusters/index#handling-ingress

It leaves me with no access to web console. The ingress controller is not exposed via VIP address to L2 network. The missing bit is adding this config after adding the IPAddressPool:

cat <<"EOF" | oc --kubeconfig ${HOSTED_CLUSTER_NAME}.kubeconfig apply
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  namespace: metallb
  name: ingress-public-advertisement
spec:
  ipAddressPools:
    - ingress-public-ip
EOF 

After applying this, OCP node starts to advertise and listen to such IP from the host network, and the system becomes operational.