OCPBUGS-45100:updating VIP details

Author: brendan-daly-red-hat

modules/installation-installer-provisioned-vsphere-config-yaml.adoc

@@ -106,6 +106,11 @@ endif::restricted[]
 <2> The `controlPlane` section is a single mapping, but the `compute` section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the `compute` section must begin with a hyphen, `-`, and the first line of the `controlPlane` section must not. Only one control plane pool is used.
 <3> The cluster name that you specified in your DNS records.
 <4> Optional: Provides additional configuration for the machine pool parameters for the compute and control plane machines.
++
+[IMPORTANT]
+====
+The VIPs, `apiVIP` and `ingressVIP`, must come from the same `networking.machineNetwork` segment. For `apiVIP` and for `ingressVIP`, if the `networking.machineNetwork` is `10.0.0.0/16` then API VIPs and Ingress VIPs must be in one of the `10.0.0.0/16` machine networks.
+====
 <5> Establishes the relationships between a region and zone. You define a failure domain by using vCenter objects, such as a `datastore` object. A failure domain defines the vCenter location for {product-title} cluster nodes.
 <6> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
 +