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

Merge pull request #87972 from openshift-cherrypick-robot/cherry-pick-85974-to-enterprise-4.18

Browse Source 
[enterprise-4.18] :updates supported roles for UDN
This commit is contained in:
Joe Aldinger
2025-02-03 14:19:27 -05:00
committed by GitHub
parent 7d17924e9f ff853b4cfa
commit 3bbffc8d18
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
modules/nw-udn-cr.adoc
View File

@@ -38,7 +38,7 @@ spec:
<1> Name of your `UserDefinedNetwork` resource. This should not be `default` or duplicate any global namespaces created by the Cluster Network Operator (CNO).
<2> The `topology` field describes the network configuration; accepted values are `Layer2` and `Layer3`. Specifying a `Layer2` topology type creates one logical switch that is shared by all nodes.
<3> This field specifies the topology configuration. It can be `layer2` or `layer3`.
<4> Specifies `Primary` or `Secondary`. `Primary` is the only `role` specification supported in 4.17.
<4> Specifies a `Primary` or `Secondary` role.
<5> For `Layer2` topology types the following specifies config details for the `subnet` field:
+
* The subnets field is optional.
@@ -69,7 +69,7 @@ spec:
<1> Name of your `UserDefinedNetwork` resource. This should not be `default` or duplicate any global namespaces created by the Cluster Network Operator (CNO).
<2> The `topology` field describes the network configuration; accepted values are `Layer2` and `Layer3`. Specifying a `Layer3` topology type creates a layer 2 segment per node, each with a different subnet. Layer 3 routing is used to interconnect node subnets.
<3> This field specifies the topology configuration. Valid values are `layer2` or `layer3`.
<4> Specifies a `Primary` or `Secondary` role. `Primary` is the only `role` specification supported in 4.17 .
<4> Specifies a `Primary` or `Secondary` role.
<5> For `Layer3` topology types the following specifies config details for the `subnet` field:
+
* The `subnets` field is mandatory.