Skip to content

Commit b02ed44

Browse files
committed
Removes "optional" and places the last sentence into an Important admonishment block.
Signed-off-by: John Wilkins <[email protected]>
1 parent 2c47cd8 commit b02ed44

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

modules/ipi-install-configure-network-components-to-run-on-the-control-plane.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,14 @@
44

55
:_content-type: PROCEDURE
66
[id='configure-network-components-to-run-on-the-control-plane_{context}']
7-
= Optional: Configuring network components to run on the control plane
7+
= Configuring network components to run on the control plane
88

9-
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. When deploying remote workers in separate subnets, you must place the `ingressVIP` virtual IP address exclusively with the control plane nodes.
9+
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.
10+
11+
[IMPORTANT]
12+
====
13+
When deploying remote workers in separate subnets, you must place the `ingressVIP` virtual IP address exclusively with the control plane nodes.
14+
====
1015

1116
image::161_OpenShift_Baremetal_IPI_Deployment_updates_0521.svg[Installer-provisioned networking]
1217

0 commit comments

Comments
 (0)