From a96c6a68466968e9539832b0853bb546ac40dca7 Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Mon, 7 Apr 2025 09:37:58 +0100 Subject: [PATCH] OSDOCS-13983: Removed localnet network as primary from UDN --- modules/nw-cluster-mtu-change.adoc | 1 - .../primary_networks/about-user-defined-networks.adoc | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/modules/nw-cluster-mtu-change.adoc b/modules/nw-cluster-mtu-change.adoc index 2e5d6aad11..f89b09c8ff 100644 --- a/modules/nw-cluster-mtu-change.adoc +++ b/modules/nw-cluster-mtu-change.adoc @@ -91,7 +91,6 @@ where: ** 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. ... Find the primary network interface by entering the following command: - + [source,terminal] ---- diff --git a/networking/multiple_networks/primary_networks/about-user-defined-networks.adoc b/networking/multiple_networks/primary_networks/about-user-defined-networks.adoc index 2b05180b6f..451ff861cb 100644 --- a/networking/multiple_networks/primary_networks/about-user-defined-networks.adoc +++ b/networking/multiple_networks/primary_networks/about-user-defined-networks.adoc @@ -10,7 +10,7 @@ Before the implementation of user-defined networks (UDN), the OVN-Kubernetes CNI 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. -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. +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. [NOTE] ====