openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPBUGS-55107:updates support matrix for localnet using NAD

Browse Source
This commit is contained in:
JoeAldinger
2025-04-17 08:53:02 -04:00
committed by openshift-cherrypick-robot
parent 45238ec8dc
commit db9e10bc8f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
modules/nw-udn-support-matrix-primary-secondary.adoc
View File

@@ -6,17 +6,17 @@
[id="support-matrix-for-udn-nad_{context}"]
= UserDefinedNetwork and NetworkAttachmentDefinition support matrix
The `UserDefinedNetwork` and `NetworkAttachmentDefinition` custom resources (CRs) provide cluster administrators and users the ability to create customizable network configurations and define their own network topologies, ensure network isolation, manage IP addressing for workloads, and configure advanced network features. A third CR, `ClusterUserDefinedNetwork`, is also available, which allows administrators the ability to create and define additional networks spanning multiple namespaces at the cluster level.
The `UserDefinedNetwork` and `NetworkAttachmentDefinition` custom resources (CRs) provide cluster administrators and users the ability to create customizable network configurations and define their own network topologies, ensure network isolation, manage IP addressing for workloads, and configure advanced network features. A third CR, `ClusterUserDefinedNetwork`, is also available, which allows administrators the ability to create and define additional networks spanning multiple namespaces at the cluster level.
User-defined networks and network attachment definitions can serve as both the primary and secondary network interface, and each support `layer2` and `layer3` topologies; a third network topology, Localnet, is also supported with network attachment definitions with secondary networks.
User-defined networks and network attachment definitions can serve as both the primary and secondary network interface, and each support `layer2` and `layer3` topologies; a third network topology, Localnet, is also supported with network attachment definitions with secondary networks.
[NOTE]
====
As of {product-title} 4.18, the Localnet topology is unavailable for use with the `UserDefinedNetwork` and `ClusterUserDefinedNetwork` CRs. It is only available for `NetworkAttachmentDefinition` CRs that leverage secondary networks.
====
The following section highlights the supported features of the `UserDefinedNetwork` and `NetworkAttachmentDefinition` CRs when they are used as either the primary or secondary network. A separate table for the `ClusterUserDefinedNetwork` CR is also included.
The following section highlights the supported features of the `UserDefinedNetwork` and `NetworkAttachmentDefinition` CRs when they are used as either the primary or secondary network. A separate table for the `ClusterUserDefinedNetwork` CR is also included.
.Primary network support matrix for `UserDefinedNetwork` and `NetworkAttachmentDefinition` CRs
[cols="1a,1a,1a, options="header"]
|===
@@ -50,7 +50,7 @@ The following section highlights the supported features of the `UserDefinedNetwo
^| ✓
^| ✓
^| `MultinetworkPolicy` resource
^| `MultinetworkPolicy` resource
^| X
^| X
@@ -71,7 +71,7 @@ The following section highlights the supported features of the `UserDefinedNetwo
^| north-south traffic
^| X
^| X
^| ✓
^| ✓ (`NetworkAttachmentDefinition` CR only)
^| Persistent IPs
^| ✓