Skip to content

Commit 5da5cb3

Browse files
author
Shikha Jhala
committed
CNV-47160: UDN support on public clouds
1 parent 1594108 commit 5da5cb3

File tree

5 files changed

+33
-3
lines changed

5 files changed

+33
-3
lines changed

_topic_maps/_topic_map_rosa.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1997,6 +1997,8 @@ Topics:
19971997
File: virt-networking-overview
19981998
- Name: Connecting a VM to the default pod network
19991999
File: virt-connecting-vm-to-default-pod-network
2000+
- Name: Connecting a VM to a primary user-defined network
2001+
File: virt-connecting-vm-to-primary-udn
20002002
- Name: Exposing a VM by using a service
20012003
File: virt-exposing-vm-with-service
20022004
# Not supported in ROSA/OSD

modules/virt-about-services.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,10 @@ ifndef::openshift-rosa,openshift-dedicated[]
2121
For on-premise clusters, you can configure a load-balancing service by deploying the MetalLB Operator.
2222
====
2323
endif::openshift-rosa,openshift-dedicated[]
24+
25+
ifdef::openshift-rosa,openshift-dedicated[]
26+
[NOTE]
27+
====
28+
For {product-rosa}, you must use `externalTrafficPolicy: Cluster` when configuring a load-balancing service, to minimize the network downtime during live migration.
29+
====
30+
endif::openshift-rosa,openshift-dedicated[]

modules/virt-networking-glossary.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@ API resource that allows you to define custom resources, or an object defined by
2020

2121
Network attachment definition (NAD):: A CRD introduced by the Multus project that allows you to attach pods, virtual machines, and virtual machine instances to one or more networks.
2222

23+
UserDefinedNetwork (UDN):: A namespace-scoped CRD introduced by the user-defined network API that can be used to create a tenant network that isolates the tenant namespace from other namespaces.
24+
25+
ClusterUserDefinedNetwork (CUDN):: A cluster-scoped CRD introduced by the user-defined network API that cluster administrators can use to create a shared network across multiple namespaces.
26+
2327
ifndef::openshift-rosa,openshift-dedicated[]
2428
Node network configuration policy (NNCP):: A CRD introduced by the nmstate project, describing the requested network configuration on nodes.
2529
You update the node network configuration, including adding and removing interfaces, by applying a `NodeNetworkConfigurationPolicy` manifest to the cluster.

virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ You can connect a virtual machine (VM) to a user-defined network (UDN) on the VM
1010

1111
{VirtProductName} supports the namespace-scoped `UserDefinedNetwork` and the cluster-scoped `ClusterUserDefinedNetwork` custom resource definitions (CRD).
1212

13-
Tenant owners can configure a primary `UserDefinedNetwork` CRD to create a network that isolates their namespace from other namespaces without requiring network policies. Cluster administrators can use the `ClusterUserDefinedNetwork` CRD to create a shared OVN network across multiple namespaces.
13+
Cluster administrators can configure a primary `UserDefinedNetwork` CRD to create a tenant network that isolates the tenant namespace from other namespaces without requiring network policies. Additionally, cluster administrators can use the `ClusterUserDefinedNetwork` CRD to create a shared OVN network across multiple namespaces.
1414

1515
[NOTE]
1616
====
@@ -65,7 +65,10 @@ include::modules/virt-creating-a-primary-cluster-udn.adoc[leveloffset=+2]
6565

6666
include::modules/virt-attaching-vm-to-primary-udn.adoc[leveloffset=+1]
6767

68+
//Excluding from ROSA because the Networking -> Multiple networks -> Primary networks section is not part of ROSA docs
69+
ifndef::openshift-rosa,openshift-dedicated[]
6870
[role="_additional-resources"]
6971
[id="additional-resources_{context}"]
7072
== Additional resources
71-
* xref:../../networking/multiple_networks/primary_networks/about-user-defined-networks.adoc#about-user-defined-networks[About user-defined networks]
73+
* xref:../../networking/multiple_networks/primary_networks/about-user-defined-networks.adoc#about-user-defined-networks[About user-defined networks]
74+
endif::openshift-rosa,openshift-dedicated[]

virt/vm_networking/virt-networking-overview.adoc

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,16 @@ image:darkcircle-6.png[20,20] The machine network can be defined over a selected
3232

3333
image:darkcircle-7.png[20,20] Secondary VM networks are typically bridged directly to a physical network, with or without VLAN encapsulation. It is also possible to create virtual overlay networks for secondary networks.
3434

35-
[NOTE]
35+
[IMPORTANT]
3636
====
3737
Connecting VMs directly to the underlay network is not supported on {product-rosa}.
3838
====
3939

40+
[NOTE]
41+
====
42+
Connecting VMs to user-defined networks with the `layer2` topology is recommended on public clouds.
43+
====
44+
4045
image:darkcircle-8.png[20,20] Secondary VM networks can be defined on dedicated set of NICs, as shown in Figure 1, or they can use the machine network.
4146

4247
include::modules/virt-networking-glossary.adoc[leveloffset=+1]
@@ -60,6 +65,15 @@ ifdef::openshift-rosa,openshift-dedicated[]
6065
You can expose a VM within the cluster or outside the cluster by creating a `Service` object.
6166
endif::openshift-rosa,openshift-dedicated[]
6267

68+
[id="primary-udn-config"]
69+
== Configuring a primary user-defined network
70+
71+
xref:../../virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc#virt-connecting-vm-to-primary-udn[Connecting a virtual machine to a primary user-defined network]::
72+
73+
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 to connect pods and VMs in selected namespaces. Cluster administrators can configure a primary `UserDefinedNetwork` CRD to create a tenant network that isolates the tenant namespace from other namespaces without requiring network policies. Additionally, cluster administrators can use the `ClusterUserDefinedNetwork` CRD to create a shared OVN `layer2` network across multiple namespaces.
74+
+
75+
User-defined networks with the `layer2` overlay topology are useful for VM workloads, and a good alternative to secondary networks in environments where physical network access is limited, such as the public cloud. The `layer2` topology enables seamless migration of VMs without the need for Network Address Translation (NAT), and also provides persistent IP addresses that are preserved between reboots and during live migration.
76+
6377
[id="secondary-network-config"]
6478
== Configuring VM secondary network interfaces
6579

0 commit comments

Comments
 (0)