Skip to content

Commit 3bde08e

Browse files
authored
Merge pull request #80609 from johnwilkins/HCIDOCS-376.1
HCIDOCS-376: Fix indents in networkConfig stanza, install-config.yml (IPI)
2 parents 9ede9fb + 0113672 commit 3bde08e

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

modules/ipi-install-configuring-host-network-interfaces-for-subnets.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,11 @@ For edge computing scenarios, it can be beneficial to locate compute nodes close
1313
When using the default load balancer, `OpenShiftManagedDefault` and adding remote nodes to your {product-title} cluster, all control plane nodes must run in the same subnet. When using more than one subnet, you can also configure the Ingress VIP to run on the control plane nodes by using a manifest. See "Configuring network components to run on the control plane" for details.
1414
====
1515

16-
If you have established different network segments or subnets for remote nodes as described in the section on "Establishing communication between subnets", you must specify the subnets in the `machineNetwork` configuration setting if the workers are using static IP addresses, bonds or other advanced networking. When setting the node IP address in the `networkConfig` parameter for each remote node, you must also specify the gateway and the DNS server for the subnet containing the control plane nodes when using static IP addresses. This ensures the remote nodes can reach the subnet containing the control plane nodes and that they can receive network traffic from the control plane.
16+
If you have established different network segments or subnets for remote nodes as described in the section on "Establishing communication between subnets", you must specify the subnets in the `machineNetwork` configuration setting if the workers are using static IP addresses, bonds or other advanced networking. When setting the node IP address in the `networkConfig` parameter for each remote node, you must also specify the gateway and the DNS server for the subnet containing the control plane nodes when using static IP addresses. This ensures that the remote nodes can reach the subnet containing the control plane and that they can receive network traffic from the control plane.
1717

1818
[NOTE]
1919
====
20-
Deploying a cluster with multiple subnets requires using virtual media, such as `redfish-virtualmedia` and `idrac-virtualmedia`, because remote nodes cannot access the local provisioning network.
20+
Deploying a cluster with multiple subnets requires using virtual media, such as `redfish-virtualmedia` or `idrac-virtualmedia`, because remote nodes cannot access the local provisioning network.
2121
====
2222

2323
.Procedure
@@ -49,10 +49,10 @@ networkConfig:
4949
- ip: <node_ip> <2>
5050
prefix-length: 24
5151
gateway: <gateway_ip> <3>
52-
dns-resolver:
53-
config:
54-
server:
55-
- <dns_ip> <4>
52+
dns-resolver:
53+
config:
54+
server:
55+
- <dns_ip> <4>
5656
----
5757
+
5858
<1> Replace `<interface_name>` with the interface name.

0 commit comments

Comments
 (0)