Skip to content

Commit

Permalink
Update clustermesh requirements to mention node InternalIP explicitly
Browse files Browse the repository at this point in the history
Discovered in community slack that k8s node ExternalIP isn't used by clustermesh even if configured.  Let's be explicit about InternalIP in the documented reqs, until such time as use of node ExternalIP is supported.

Signed-off-by: Jef Spaleta <jspaleta@gmail.com>
  • Loading branch information
jspaleta authored and jrajahalme committed Mar 10, 2023
1 parent eff384c commit 7dbc63a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Documentation/network/clustermesh/clustermesh.rst
Original file line number Diff line number Diff line change
Expand Up @@ -29,9 +29,9 @@ Cluster Addressing Requirements
* PodCIDR ranges in all clusters and all nodes must be non-conflicting and
unique IP addresses.

* Nodes in all clusters must have IP connectivity between each other. This
requirement is typically met by establishing peering or VPN tunnels between
the networks of the nodes of each cluster.
* Nodes in all clusters must have IP connectivity between each other using the
configured InternalIP for each node. This requirement is typically met by establishing
peering or VPN tunnels between the networks of the nodes of each cluster.

* The network between clusters must allow the inter-cluster communication. The
exact ports are documented in the :ref:`firewall_requirements` section.
Expand Down

0 comments on commit 7dbc63a

Please sign in to comment.