Merge pull request #89337 from stevsmit/OSDOCS-13139

UI procedures for UDN and CUDN

Author: stevsmit

modules/nw-cudn-cr-ui.adoc

@@ -0,0 +1,28 @@
+// Module included in the following assemblies:
+//
+// * networking/multiple_networks/primary_networks/about-user-defined-networks.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="nw-cudn-cr-ui_{context}"]
+= Creating a ClusterUserDefinedNetwork CR by using the web console
+
+You can create a `ClusterUserDefinedNetwork` custom resource (CR) in the {product-title} web console.
+
+.Prerequisites
+
+* You have access to the {product-title} web console as a user with `cluster-admin` permissions.
+* You have created a namespace and applied the `k8s.ovn.org/primary-user-defined-network` label.
+
+.Procedure
+
+. From the *Administrator* perspective, click *Networking* -> *UserDefinedNetworks*.
+
+. Click *ClusterUserDefinedNetwork*.
+
+. In the *Name* field, specify a name for the cluster-scoped UDN.
+
+. Specify a value in the *Subnet* field.
+
+. In the *Project(s) Match Labels* field, add the appropriate labels to select namespaces that the cluster UDN applies to.
+
+. Click *Create*. The cluster-scoped UDN serves as the default primary network for pods located in namespaces that contain the labels that you specified in step 5.

modules/nw-cudn-cr.adoc

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="nw-cudn-cr_{context}"]
-= Creating a ClusterUserDefinedNetwork CR
+= Creating a ClusterUserDefinedNetwork CR by using the CLI
 
-The following procedure creates a `ClusterUserDefinedNetwork` custom resource (CR). Based upon your use case, create your request using either the `cluster-layer-two-udn.yaml` example for a `Layer2` topology type or the `cluster-layer-three-udn.yaml` example for a `Layer3` topology type.
+The following procedure creates a `ClusterUserDefinedNetwork` custom resource (CR) by using the CLI. Based upon your use case, create your request using either the `cluster-layer-two-udn.yaml` example for a `Layer2` topology type or the `cluster-layer-three-udn.yaml` example for a `Layer3` topology type.
 
 [IMPORTANT]
 ====

modules/nw-udn-cr-ui.adoc

@@ -0,0 +1,26 @@
+// Module included in the following assemblies:
+//
+// * networking/multiple_networks/primary_networks/about-user-defined-networks.adoc
+
+:_mod-docs-content-type: PROCEDURE                                    
+[id="nw-udn-cr-ui_{context}"]                                   
+= Creating a UserDefinedNetwork CR by using the web console
+
+You can create a `UserDefinedNetwork` custom resource by using the {product-title} web console.
+
+.Prerequisites
+
+* You have access to the {product-title} web console as a user with `cluster-admin` permissions.
+* You have created a namespace and applied the `k8s.ovn.org/primary-user-defined-network` label.
+
+.Procedure
+
+. From the *Administrator* perspective, click *Networking* -> *UserDefinedNetworks*.
+
+. Click *Create UserDefinedNetwork*.
+
+. From the *Project name* list, select the namespace that you previously created.
+
+. Specify a value in the *Subnet* field.
+
+. Click *Create*. The user-defined network serves as the default primary network for pods that you create in this namespace.

modules/nw-udn-cr.adoc

@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="nw-udn-cr_{context}"]
-= Creating a UserDefinedNetwork custom resource
+= Creating a UserDefinedNetwork CR by using the CLI
 
 The following procedure creates a `UserDefinedNetwork` CR that is namespace scoped. Based upon your use case, create your request by using either the `my-layer-two-udn.yaml` example for a `Layer2` topology type or the `my-layer-three-udn.yaml` example for a `Layer3` topology type.
 

modules/virt-creating-primary-cluster-udn-web.adoc

@@ -2,8 +2,8 @@
 //
 // * virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc              
 
-:_mod-docs-content-type: PROCEDURE                                    
-[id="virt-creating-primary-cluster-udn-web_{context}"]                                   
+:_mod-docs-content-type: PROCEDURE
+[id="virt-creating-primary-cluster-udn-web_{context}"]
 = Creating a primary cluster-scoped user-defined network by using the web console
 
 You can connect multiple namespaces to the same primary user-defined network (UDN) by creating a `ClusterUserDefinedNetwork` custom resource in the {product-title} web console.

networking/multiple_networks/primary_networks/about-user-defined-networks.adoc

@@ -33,9 +33,12 @@ include::modules/nw-cudn-about.adoc[leveloffset=+1]
 //Best practices for using CUDN.
 include::modules/nw-cudn-best-practices.adoc[leveloffset=+2]
 
-//How to implement the CUDN API on a cluster.
+//How to implement the CUDN API on a cluster by using the CLI.
 include::modules/nw-cudn-cr.adoc[leveloffset=+2]
 
+//How to implement the CUDN API on a cluster by using the UI.
+include::modules/nw-cudn-cr-ui.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../../networking/multiple_networks/secondary_networks/creating-secondary-nwt-ovnk.adoc#configuring-pods-static-ip_configuring-additional-network-ovnk[Configuring pods with a static IP address]
@@ -46,11 +49,14 @@ include::modules/nw-udn-about.adoc[leveloffset=+1]
 //Best practices for using UDN.
 include::modules/nw-udn-best-practices.adoc[leveloffset=+2]
 
-//How to implement the UDN API on a cluster.
+//How to implement the UDN API by using the CLI.
 include::modules/nw-udn-cr.adoc[leveloffset=+2]
 
+//How to implement the UDN API by using the UI
+include::modules/nw-udn-cr-ui.adoc[leveloffset=+2]
+
 //Explanation of optional config details
-include::modules/nw-udn-additional-config-details.adoc[leveloffset=+2]
+include::modules/nw-udn-additional-config-details.adoc[leveloffset=+1]
 
 //UDN/CUDN status conditions
 include::modules/cudn-status-conditions.adoc[leveloffset=+1]