Merge pull request #33586 from johnwilkins/TELCODOCS-113

bergerhoffer · web-flow · commit 69823f208c33 · 2021-06-17T12:56:44.000-04:00
TELCODOCS-113: KNIDEPLOY-4421, Allow customers to use their own LB for external api/ingress traffic
diff --git a/modules/nw-enabling-a-provisioning-network-after-installation.adoc b/modules/nw-enabling-a-provisioning-network-after-installation.adoc
@@ -12,16 +12,16 @@ In {product-title} 4.8 and later, you can enable a `provisioning` network after
 
 .Prerequisites
 
-. The `provisioning` network must exist.
-. The `provisioning` network must be enabled.
-. The cluster nodes must be connected to the `provisioning` network using the same network interface on both worker nodes and control plane nodes.
-. The cluster nodes must be homogeneous. If the cluster nodes use different network interface names for the same network interface order, such as `eth0` and `eno1` for the first network interface, the procedure fails.
+* A dedicated physical network must exist, connected to all worker and control plane nodes.
+* You must isolate the native, untagged physical network.
+* The network cannot have a DHCP server when the `provisioningNetwork` configuration setting is set to `Managed`.
+* You must connect the control plane nodes to the network with the same network interface, such as `eth0` or `eno1`.
 
 .Procedure
 
 . Identify the provisioning interface name for the cluster nodes. For example, `eth0` or `eno1`.
 
-. Enable the preboot execution environment (PXE) on the `provisioning` network interface of the cluster nodes.
+. Enable the Preboot eXecution Environment (PXE) on the `provisioning` network interface of the cluster nodes.
 
 . Retrieve the current state of the `provisioning` network and save it to a provisioning configuration resource file:
 +
@@ -59,7 +59,7 @@ items:
 +
 where:
 +
-<1> The `provisioningNetwork` is one of `Managed`, `Unmanaged`, or `Disabled`. When set to `Managed`, Metal3 manages the provisioning network and the CBO deploys the Metal3 pod with a configured DHCP server. When set to `Unmanaged`, the system administrator configures DHCP server manually.
+<1> The `provisioningNetwork` is one of `Managed`, `Unmanaged`, or `Disabled`. When set to `Managed`, Metal3 manages the provisioning network and the CBO deploys the Metal3 pod with a configured DHCP server. When set to `Unmanaged`, the system administrator configures the DHCP server manually.
 +
 <2> The `provisioningOSDownloadURL` is a valid HTTPS URL with a valid sha256 checksum that enables the Metal3 pod to download a qcow2 operating system image ending in `.qcow2.gz` or `.qcow2.xz`. This field is required whether the provisioning network is `Managed`, `Unmanaged`, or `Disabled`. For example: `\http://192.168.0.1/images/rhcos-_<version>_.x86_64.qcow2.gz?sha256=_<sha>_`.
 +

Original file line number	Diff line number	Diff line change
@@ -12,16 +12,16 @@ In {product-title} 4.8 and later, you can enable a `provisioning` network after
`12`	`12`
`13`	`13`	`.Prerequisites`
`14`	`14`
`15`		-. The `provisioning` network must exist.
`16`		-. The `provisioning` network must be enabled.
`17`		-. The cluster nodes must be connected to the `provisioning` network using the same network interface on both worker nodes and control plane nodes.
`18`		-. The cluster nodes must be homogeneous. If the cluster nodes use different network interface names for the same network interface order, such as `eth0` and `eno1` for the first network interface, the procedure fails.
	`15`	`+* A dedicated physical network must exist, connected to all worker and control plane nodes.`
	`16`	`+* You must isolate the native, untagged physical network.`
	`17`	+* The network cannot have a DHCP server when the `provisioningNetwork` configuration setting is set to `Managed`.
	`18`	+* You must connect the control plane nodes to the network with the same network interface, such as `eth0` or `eno1`.
`19`	`19`
`20`	`20`	`.Procedure`
`21`	`21`
`22`	`22`	. Identify the provisioning interface name for the cluster nodes. For example, `eth0` or `eno1`.
`23`	`23`
`24`		-. Enable the preboot execution environment (PXE) on the `provisioning` network interface of the cluster nodes.
	`24`	+. Enable the Preboot eXecution Environment (PXE) on the `provisioning` network interface of the cluster nodes.
`25`	`25`
`26`	`26`	. Retrieve the current state of the `provisioning` network and save it to a provisioning configuration resource file:
`27`	`27`	`+`
`@@ -59,7 +59,7 @@ items:`
`59`	`59`	`+`
`60`	`60`	`where:`
`61`	`61`	`+`
`62`		-<1> The `provisioningNetwork` is one of `Managed`, `Unmanaged`, or `Disabled`. When set to `Managed`, Metal3 manages the provisioning network and the CBO deploys the Metal3 pod with a configured DHCP server. When set to `Unmanaged`, the system administrator configures DHCP server manually.
	`62`	+<1> The `provisioningNetwork` is one of `Managed`, `Unmanaged`, or `Disabled`. When set to `Managed`, Metal3 manages the provisioning network and the CBO deploys the Metal3 pod with a configured DHCP server. When set to `Unmanaged`, the system administrator configures the DHCP server manually.
`63`	`63`	`+`
`64`	`64`	<2> The `provisioningOSDownloadURL` is a valid HTTPS URL with a valid sha256 checksum that enables the Metal3 pod to download a qcow2 operating system image ending in `.qcow2.gz` or `.qcow2.xz`. This field is required whether the provisioning network is `Managed`, `Unmanaged`, or `Disabled`. For example: `\http://192.168.0.1/images/rhcos-_<version>_.x86_64.qcow2.gz?sha256=_<sha>_`.
`65`	`65`	`+`