Skip to content

Commit b8a0aca

Browse files
authored
Merge pull request #91697 from dfitzmau/OSDOCS-13983
OSDOCS-13983: Removed localnet network as primary from UDN
2 parents 4c72cdc + f3e4c95 commit b8a0aca

File tree

2 files changed

+1
-2
lines changed

2 files changed

+1
-2
lines changed

modules/nw-cluster-mtu-change.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,6 @@ where:
9191
** If your hardware MTU is specified in a NetworkManager connection configuration, complete the following steps. This approach is the default for {product-title} if you do not explicitly specify your network configuration with DHCP, a kernel command line, or some other method. Your cluster nodes must all use the same underlying network configuration for the following procedure to work unmodified.
9292

9393
... Find the primary network interface by entering the following command:
94-
9594
+
9695
[source,terminal]
9796
----

networking/multiple_networks/primary_networks/about-user-defined-networks.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Before the implementation of user-defined networks (UDN), the OVN-Kubernetes CNI
1010

1111
While the Kubernetes design is useful for simple deployments, this Layer 3 topology restricts customization of primary network segment configurations, especially for modern multi-tenant deployments.
1212

13-
UDN improves the flexibility and segmentation capabilities of the default Layer 3 topology for a Kubernetes pod network by enabling custom Layer 2, Layer 3, and localnet network segments, where all these segments are isolated by default. These segments act as either primary or secondary networks for container pods and virtual machines that use the default OVN-Kubernetes CNI plugin. UDNs enable a wide range of network architectures and topologies, enhancing network flexibility, security, and performance.
13+
UDN improves the flexibility and segmentation capabilities of the default Layer 3 topology for a Kubernetes pod network by enabling custom Layer 2 and Layer 3 network segments, where all these segments are isolated by default. These segments act as either primary or secondary networks for container pods and virtual machines that use the default OVN-Kubernetes CNI plugin. UDNs enable a wide range of network architectures and topologies, enhancing network flexibility, security, and performance.
1414

1515
[NOTE]
1616
====

0 commit comments

Comments
 (0)