|CNI||Container Networking Interface, a specification of a standardized interface defining the container endpoint and its interaction with the node the container runs on.|
|Docker||A popular container runtime.|
|vSwitch||Virtual Switch, the central component in container networking. Every container host has one. It serves up the basic connectivity for each container endpoint. On the Linux side it resembles somewhat to a Linux Bridge.|
|NAT||Network Address Translation. A way to isolate private IP address spaces across multiple hosts and nodes behind a public IP Address space|
|Pod||the smallest atomic unit in a Kubernetes Cluster. A Pod can host one or more containers. All Containers in a pod share the same IP address|
|Node||An infrastructure component hosting one or more pods.|
|Cluster||An infrastructure component comprised of multiple nodes.|
|HNS||Host Network Service, a windows component interacting with the networking aspects of the Windows container infrastructure|
|HCS||Host Compute Service, a Windows component supporting the interactions of the container runtime with the rest of the operating system|
Open Virtual Network. OVN provides network virtualization to containers. In the "overlay" mode, OVN can create a logical network amongst containers running on multiple hosts. In this mode, OVN programs the Open vSwitch instances running inside your hosts. These hosts can be bare-metal machines or vanilla VMs. OVN uses two data stores the Northbound (OVN-NB) and the Southbound (OVN-SB) data store.
|OVS||Open Virtual Switch. Open vSwitch is well suited to function as a virtual switch in VM environments. In addition to exposing standard control and visibility interfaces to the virtual networking layer, it was designed to support distribution across multiple physical servers.|
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.