1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

CNV-43385: Added networking architecture diagram

This commit is contained in:
Shikha Jhala
2024-07-22 15:29:00 -04:00
parent d77272143f
commit b836a1237e
2 changed files with 21 additions and 0 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 88 KiB

View File

@@ -13,6 +13,27 @@ toc::[]
You cannot run {VirtProductName} on a single-stack IPv6 cluster.
====
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]