mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
16 lines
1.2 KiB
Plaintext
16 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * network_observability/observing-network-traffic.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="network-observability-user-defined-networks_{context}"]
|
|
= User-defined networks
|
|
|
|
[role="_abstract"]
|
|
Understand how you can use user-defined networks (UDN) for flexible network segmentation and leverage the Network Observability Operator to monitor these segments through dedicated labels and name filters in the traffic flow table.
|
|
|
|
User-defined networks (UDN) improve 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 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.
|
|
|
|
When the `UDNMapping` feature is enabled with Network Observability, the *Traffic* flow table has a *UDN labels* column. You can filter on *Source Network Name* and *Destination Network Name*. |