You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/virt-attaching-vm-to-primary-udn.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
:_mod-docs-content-type: PROCEDURE
6
6
[id="virt-attaching-vm-to-primary-udn_{context}"]
7
-
= Attaching a virtual machine to the primary user-defined network
7
+
= Attaching a virtual machine to the primary user-defined network by using the CLI
8
8
9
9
You can connect a virtual machine (VM) to the primary user-defined network (UDN) by requesting the pod network attachment, and configuring the interface binding.
Copy file name to clipboardExpand all lines: modules/virt-creating-a-primary-udn.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@
4
4
5
5
:_mod-docs-content-type: PROCEDURE
6
6
[id="virt-creating-a-primary-udn_{context}"]
7
-
= Creating a primary namespace-scoped user-defined network
7
+
= Creating a primary namespace-scoped user-defined network by using the CLI
8
8
9
-
You can create an isolated primary network in your project namespace. You must use the OVN-Kubernetes layer 2 topology and enable persistent IP address allocation in the user-defined network (UDN) configuration to ensure VM live migration support.
9
+
You can create an isolated primary network in your project namespace by using the CLI. You must use the OVN-Kubernetes layer 2 topology and enable persistent IP address allocation in the user-defined network (UDN) configuration to ensure VM live migration support.
= Creating a primary cluster-scoped user-defined network by using the web console
8
+
9
+
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.
10
+
11
+
.Prerequisites
12
+
* You have access to the {product-title} web console as a user with `cluster-admin` permissions.
13
+
14
+
.Procedure
15
+
. From the *Administrator* perspective, click *Networking*->*UserDefinedNetworks*.
16
+
17
+
. From the *Create* list, select *ClusterUserDefinedNetwork*.
18
+
19
+
. In the *Name* field, specify a name for the cluster-scoped UDN.
20
+
21
+
. Specify a value in the *Subnet* field.
22
+
23
+
. In the *Project(s) Match Labels* field, add the appropriate labels to select namespaces that the cluster UDN applies to.
24
+
25
+
. Click *Create*. The cluster-scoped UDN serves as the default primary network for pods and virtual machines located in namespaces that contain the labels that you specified in step 5.
= Creating a primary namespace-scoped user-defined network by using the web console
8
+
9
+
You can create an isolated primary network in your project namespace by creating a `UserDefinedNetwork` custom resource in the {product-title} web console.
10
+
11
+
.Prerequisites
12
+
* You have access to the {product-title} web console as a user with `cluster-admin` permissions.
13
+
* You have created a namespace and applied the `k8s.ovn.org/primary-user-defined-network` label. For more information, see "Creating a namespace for user-defined networks by using the web console".
14
+
15
+
.Procedure
16
+
. From the *Administrator* perspective, click *Networking*->*UserDefinedNetworks*.
17
+
18
+
. Click *Create UserDefinedNetwork*.
19
+
20
+
. From the *Project name* list, select the namespace that you previously created.
21
+
22
+
. Specify a value in the *Subnet* field.
23
+
24
+
. Click *Create*. The user-defined network serves as the default primary network for pods and virtual machines that you create in this namespace.
<1> This label is required for the namespace to be associated with a UDN. If the namespace is to be used with an existing cluster UDN, you must also add the appropriate labels that are defined in the `spec.namespaceSelector` field of the `ClusterUserDefinedNetwork` custom resource.
30
+
31
+
. Apply the `Namespace` manifest by running the following command:
= Creating a namespace for user-defined networks by using the web console
8
+
9
+
You can create a namespace to be used with primary user-defined networks (UDNs) by using the {product-title} web console.
10
+
11
+
.Prerequisites
12
+
* Log in to the {product-title} web console as a user with `cluster-admin` permissions.
13
+
14
+
15
+
.Procedure
16
+
. From the *Administrator* perspective, click *Administration*->*Namespaces*.
17
+
18
+
. Click *Create Namespace*.
19
+
20
+
. In the *Name* field, specify a name for the namespace. The name must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character.
21
+
22
+
. In the *Labels* field, add the `k8s.ovn.org/primary-user-defined-network` label.
23
+
24
+
. Optional: If the namespace is to be used with an existing cluster-scoped UDN, add the appropriate labels as defined in the `spec.namespaceSelector` field in the `ClusterUserDefinedNetwork` custom resource.
You can connect a virtual machine (VM) to a user-defined network (UDN) on the VM's primary interface. The primary user-defined network replaces the default pod network in your specified namespace. Unlike the pod network, you can define the primary UDN per project, where each project can use its specific subnet and topology.
9
+
You can connect a virtual machine (VM) to a user-defined network (UDN) on the VM's primary interface by using the {product-title} web console or the CLI. The primary user-defined network replaces the default pod network in your specified namespace. Unlike the pod network, you can define the primary UDN per project, where each project can use its specific subnet and topology.
10
10
11
11
{VirtProductName} supports the namespace-scoped `UserDefinedNetwork` and the cluster-scoped `ClusterUserDefinedNetwork` custom resource definitions (CRD).
12
12
@@ -33,9 +33,35 @@ You must consider the following limitations before implementing a primary UDN:
33
33
{VirtProductName} currently does not support secondary user-defined networks.
You can use the {product-title} web console to create a primary namespace-scoped `UserDefinedNetwork` or a cluster-scoped `ClusterUserDefinedNetwork` CRD. The UDN serves as the default primary network for pods and VMs that you create in namespaces associated with the network.
* xref:../../virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc#virt-creating-udn-namespace-web_virt-connecting-vm-to-primary-udn[Create namespaces that are associated with the cluster-scoped UDN]
50
+
51
+
[id="creating-primary-udn-cli_{context}"]
52
+
== Creating a primary user-defined network by using the CLI
53
+
54
+
You can create a primary `UserDefinedNetwork` or `ClusterUserDefinedNetwork` CRD by using the CLI.
* xref:../../virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc#virt-creating-udn-namespace-cli_virt-connecting-vm-to-primary-udn[Create namespaces that are associated with the cluster-scoped UDN]
0 commit comments