The OpenShift-Installer does not validate if the apiVIPs and ingressVIPs are specified when the load balancer is configured as UserManaged and fall back to the default behaviour where it picks the 5th and 7th IPs of the machine network

    4.18

    100%

1. Create an install-config.yaml file with the following content:

$ cat ocp4/install-config.yaml

apiVersion: v1
baseDomain: mydomain.test
compute:
- name: worker
  platform:
    openstack:
      type: m1.xlarge
  replicas: 3
controlPlane:
  name: master
  platform:
    openstack:
      type: m1.xlarge
  replicas: 3
metadata:
  name: mycluster
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 192.168.10.0/24
platform:
  openstack:
    loadBalancer:
      type: UserManaged


2. Run the following command to generate manifests:
$ openshift-installer create manifests --dir ocp4

3. Check the generated cluster-config.yaml:
$ cat ocp4/manifests/cluster-config.yaml     

4.Observe the following unexpected output:
platform:
  openstack:
    cloud: openstack
    externalDNS: null
    apiVIPs:
    - 192.168.10.5
    ingressVIPs:
    - 192.168.10.7
    loadBalancer:
      type: UserManaged

    The apiVIPs and ingressVIPs fields are unexpectedly added to cluster-config.yaml.

The apiVIPs and ingressVIPs fields should not be automatically assigned.