Merge pull request #56766 from snarayan-redhat/OSDOCS-5116_remoteworkers

OSDOCS-5116: Support remote workers for vSphere

Author: snarayan-redhat

images/325_OpenShift_vSphere_Deployment_updates_0323.png

@@ -94,6 +94,7 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 * See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service
 
 include::modules/nw-osp-configuring-external-load-balancer.adoc[leveloffset=+1]
+include::modules/ipi-install-configure-network-components-to-run-on-the-control-plane.adoc[leveloffset=+1]
 
 == Next steps
 

installing/installing_vsphere/installing-vsphere-installer-provisioned-network-customizations.adoc

@@ -1,19 +1,37 @@
 // This is included in the following assemblies:
 //
 // ipi-install-configuration-files.adoc
+ifeval::["{context}" == "ipi-install-installation-workflow"]
+:bare:
+endif::[]
+ifeval::["{context}" == "installing-vsphere-installer-provisioned-network-customizations"]
+:vSphere:
+endif::[]
 
 :_content-type: PROCEDURE
 [id='configure-network-components-to-run-on-the-control-plane_{context}']
 = Configuring network components to run on the control plane
 
-You can configure networking components to run exclusively on the control plane nodes. By default, {product-title} allows any node in the machine config pool to host the `ingressVIP` virtual IP address. However, some environments deploy worker nodes in separate subnets from the control plane nodes, which requires configuring the `ingressVIP` virtual IP address to run on the control plane nodes. 
+You can configure networking components to run exclusively on the control plane nodes. By default, {product-title} allows any node in the machine config pool to host the `ingressVIP` virtual IP address. However, some environments deploy worker nodes in separate subnets from the control plane nodes, which requires configuring the `ingressVIP` virtual IP address to run on the control plane nodes.
+
+ifdef::vSphere[]
+[NOTE]
+====
+You can scale the remote workers by creating a worker machineset in a separate subnet.
+====
+endif::vSphere[]
 
 [IMPORTANT]
 ====
 When deploying remote workers in separate subnets, you must place the `ingressVIP` virtual IP address exclusively with the control plane nodes.
 ====
 
+ifdef::bare[]
 image::161_OpenShift_Baremetal_IPI_Deployment_updates_0521.svg[Installer-provisioned networking]
+endif::bare[]
+ifdef::vSphere[]
+image::325_OpenShift_vSphere_Deployment_updates_0323.png[Installer-provisioned networking]
+endif::vSphere[]
 
 .Procedure
 
@@ -96,3 +114,10 @@ $ sed -i "s;mastersSchedulable: false;mastersSchedulable: true;g" clusterconfigs
 ====
 If control plane nodes are not schedulable after completing this procedure, deploying the cluster will fail.
 ====
+
+ifeval::["{context}" == "ipi-install-installation-workflow"]
+:!bare:
+endif::[]
+ifeval::["{context}" == "installing-vsphere-installer-provisioned-network-customizations"]
+:!vSphere:
+endif::[]