Merge pull request #95180 from sjhala-ccs/cnv-64163

CNV-64163: Fixed namespace value in localnet UDN doc

Author: sjhala-ccs

modules/virt-attaching-vm-to-secondary-udn.adoc

@@ -21,7 +21,7 @@ apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   name: example-vm
-  namespace: my-namespace # <1>
+  namespace: red # <1>
 spec:
   template:
     spec:

modules/virt-creating-secondary-localnet-udn.adoc

@@ -29,13 +29,13 @@ spec:
   desiredState:
     ovn:
       bridge-mappings:
-      - localnet: tenantblue # <3>
+      - localnet: localnet1 # <3>
         bridge: br-ex # <4>
         state: present # <5>
 ----
 <1> The name of the configuration object.
 <2> Specifies the nodes to which the node network configuration policy is applied. The recommended node selector value is `node-role.kubernetes.io/worker: ''`.
-<3> The name of the additional network from which traffic is forwarded to the OVS bridge. This attribute must match the value of the `spec.network.localnet.physicalNetworkName` field of the `ClusterUserDefinedNetwork` object that defines the OVN-Kubernetes additional network. This example uses the name `tenantblue`.
+<3> The name of the additional network from which traffic is forwarded to the OVS bridge. This attribute must match the value of the `spec.network.localnet.physicalNetworkName` field of the `ClusterUserDefinedNetwork` object that defines the OVN-Kubernetes additional network. This example uses the name `localnet1`.
 <4> The name of the OVS bridge on the node. This value is required if the `state` attribute is `present` or not specified.
 <5> The state of the mapping. Must be either `present` to add the mapping or `absent` to remove the mapping. The default value is `present`.
 +
@@ -74,7 +74,7 @@ spec:
     topology: Localnet # <5>
     localnet:
         role: Secondary # <6>
-        physicalNetworkName: tenantblue # <7>
+        physicalNetworkName: localnet1 # <7>
         ipam:
           mode: Disabled # <8>
 # ...

modules/virt-creating-secondary-udn-namespace.adoc

@@ -22,7 +22,7 @@ You can create a namespace to be used with an existing secondary cluster-scoped
 apiVersion: v1
 kind: Namespace
 metadata:
-  name: cudn_namespace
+  name: red
 # ...
 ----