When using a UserManaged load balancer in OpenShift, the validation process still checks for VIPs (Virtual IPs). This causes an error, requiring the customer to append a machineNetwork associated with the VIPs to workaround the validation process. This is not expected behavior as the customer is managing the load balancer manually.

Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster:
Error on validating API VIPs and Machine Networks: VIP '10.1.106.xx' cannot be found in any machine network

    4.16.x

    always

    1. Configure OpenShift with a UserManaged load balancer.
    2. Ensure the VIPs are outside of any machineNetwork CIDR.
    3. Attempt installation
    

    The configuration process fails with an error stating that the VIP cannot be found in any machine network.

$ oc get co/network NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE network 4.16.7 True False True 152m Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster: Error on validating API VIPs and Machine Networks: VIP '10.1.106.xx' cannot be found in any machine network

    Since the load balancer is UserManaged, the validation should not require the VIP to be part of any machineNetwork CIDR.

Baremetal IPI installation:

      platformSpec:
    baremetal:
      apiServerInternalIPs:
        - 10.1.106.xx
      ingressIPs:
        - 10.1.106.xx
      machineNetworks:
        - 10.1.104.0/23
        - 10.1.106.0/24 <=== Added to workaround the issue