Skip to content

Commit 9794087

Browse files
committed
OCPBUGS-55288: Added note about bonded interface and node IP address issues
1 parent 543efe7 commit 9794087

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

modules/ipi-install-establishing-communication-between-subnets.adoc

+6-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,12 @@
88

99
In a typical {product-title} cluster setup, all nodes, including the control plane and compute nodes, reside in the same network. However, for edge computing scenarios, it can be beneficial to locate compute nodes closer to the edge. This often involves using different network segments or subnets for the remote nodes than the subnet used by the control plane and local compute nodes. Such a setup can reduce latency for the edge and allow for enhanced scalability.
1010

11-
Before installing {product-title}, you must configure the network properly to ensure that the edge subnets containing the remote nodes can reach the subnet containing the control plane nodes and receive traffic from the control plane too.
11+
Before installing {product-title}, you must configure the network properly to ensure that the edge subnets containing the remote nodes can reach the subnet containing the control plane nodes and receive traffic from the control plane too.
12+
13+
[IMPORTANT]
14+
====
15+
For a {product-title} cluster that is built with {op-system-base-full} and has a network that includes a bonded interface, the Network Manager might temporarily assign the wrong IP to nodes that run on network interfaces if `nodeip-configuration.service` starts before `nmstate`. This situation can cause nodes to remain stuck. As a workaround for this issue, reboot each node, specify the correct IP address in `/run/nodeip-configuration/primary-ip`, and restart the `wait-for-primary-ip` service.
16+
====
1217

1318
You can run control plane nodes in the same subnet or multiple subnets by configuring a user-managed load balancer in place of the default load balancer. With a multiple subnet environment, you can reduce the risk of your {product-title} cluster from failing because of a hardware failure or a network outage. For more information, see "Services for a user-managed load balancer" and "Configuring a user-managed load balancer".
1419

0 commit comments

Comments
 (0)