CNV-43385: Added networking architecture diagram

Author: Shikha Jhala

images/318_OpenShift_Virtualization_Networking_0423.png

@@ -8,6 +8,27 @@ toc::[]
 
 {VirtProductName} provides advanced networking functionality by using custom resources and plugins. Virtual machines (VMs) are integrated with {product-title} networking and its ecosystem.
 
+The following figure illustrates the typical network setup of {VirtProductName}. Other configurations are also possible.
+
+.{VirtProductName} networking overview
+image::318_OpenShift_Virtualization_Networking_0423.png[{VirtProductName} networking architecture]
+
+image:darkcircle-1.png[20,20] Pods and VMs run on the same network infrastructure which allows you to easily connect your containerized and virtualized workloads.
+
+image:darkcircle-2.png[20,20] You can connect VMs to the default pod network and to any number of secondary networks.
+
+image:darkcircle-3.png[20,20] The default pod network provides connectivity between all its members, service abstraction, IP management, micro segmentation, and other functionality.
+
+image:darkcircle-4.png[20,20] Multus is a "meta" CNI plugin that enables a pod or virtual machine to connect to additional network interfaces by using other compatible CNI plugins.
+
+image:darkcircle-5.png[20,20] The default pod network is overlay-based, tunneled through the underlying machine network.
+
+image:darkcircle-6.png[20,20] The machine network can be defined over a selected set of network interface controllers (NICs).
+
+image:darkcircle-7.png[20,20] Secondary VM networks are typically bridged directly to a physical network, with or without VLAN encapsulation.
+
+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.
+
 include::modules/virt-networking-glossary.adoc[leveloffset=+1]