Skip to content

Commit 583cd90

Browse files
authored
Merge pull request #97350 from JoeAldinger/OSDOCS-15772
OSDOCS-15772:CQA work for UDN docs
2 parents 14cadf0 + 3cf04b9 commit 583cd90

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

modules/nw-cudn-cr.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ metadata:
3434
EOF
3535
----
3636

37-
. Create a request for either a `Layer2` or `Layer3` topology type cluster-wide user-defined network:
37+
. Create a cluster-wide user-defined network for either a `Layer2` or `Layer3` topology type:
3838

3939
.. Create a YAML file, such as `cluster-layer-two-udn.yaml`, to define your request for a `Layer2` topology as in the following example:
4040
+
@@ -58,9 +58,9 @@ spec:
5858
- "10.100.0.0/16" # <9>
5959
----
6060
<1> Name of your `ClusterUserDefinedNetwork` CR.
61-
<2> A label query over the set of namespaces that the cluster UDN CR applies to. Uses the standard Kubernetes `MatchLabel` selector. Must not point to `default` or `openshift-*` namespaces.
61+
<2> A label query over the set of namespaces that the CUDN CR applies to. Uses the standard Kubernetes `MatchLabel` selector. Must not point to `default` or `openshift-*` namespaces.
6262
<3> Uses the `matchLabels` selector type, where terms are evaluated with an `AND` relationship.
63-
<4> Because the `matchLabels` selector type is used, provisions namespaces that contain both `<label_1_key>=<label_1_value>` and `<label_2_key>=<label_2_value>` labels.
63+
<4> In this example, the CUDN CR is deployed to namespaces that contain both `<label_1_key>=<label_1_value>` and `<label_2_key>=<label_2_value>` labels.
6464
<5> Describes the network configuration.
6565
<6> 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.
6666
<7> This field specifies the topology configuration. It can be `layer2` or `layer3`.

modules/nw-udn-cr.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ metadata:
2929
EOF
3030
----
3131

32-
. Create a request for either a `Layer2` or `Layer3` topology type user-defined network:
32+
. Create a user-defined network for either a `Layer2` or `Layer3` topology type:
3333

3434
.. Create a YAML file, such as `my-layer-two-udn.yaml`, to define your request for a `Layer2` topology as in the following example:
3535
+

0 commit comments

Comments
 (0)