vSphere with Tanzu introduces a new construct that is called vSphere Pod, which is the equivalent of a Kubernetes pod. A vSphere Pod is a VM with a small footprint that runs one or more Linux containers. Each vSphere Pod is sized precisely for the workload that it accommodates and has explicit resource reservations for that workload. It allocates the exact amount of storage, memory, and CPU resources required for the workload to run. vSphere Pods are only supported with Supervisor Clusters that are configured with NSX-T Data Center as the networking stack.
- Strong isolation. A vSphere Pod is isolated in the same manner as a virtual machine. Each vSphere Pod has its own unique Linux kernel that is based on the kernel used in Photon OS. Rather than many containers sharing a kernel, as in a bare metal configuration, in a vSphere Pod, each container has a unique Linux kernel
- Resource Management. vSphere DRS handles the placement of vSphere Pods on the Supervisor Cluster.
- High performance. vSphere Pods get the same level of resource isolation as VMs, eliminating noisy neighbor problems while maintaining the fast start-up time and low overhead of containers.
- Diagnostics. As a vSphere administrator you can use all the monitoring and introspection tools that are available with vSphere on workloads.
For networking, vSphere Pods and the VMs of the Tanzu Kubernetes clusters created through the Tanzu Kubernetes Grid Service use the topology provided by NSX-T Data Center. For details, see Supervisor Cluster Networking.
vSphere Pods are only supported on Supervisor Clusters that use NSX-T Data Center as their networking stack. They are not supported on clusters that are configured with the vSphere networking stack.