vSphere with Kubernetes introduces a new construct 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.

Figure 1. vSphere Pods
vSphere Pods are objects in vCenter Server, and therefore enable the following capabilities for workloads:
  • Strong isolation. Every vSphere Pod has a Linux kernel, which provides isolation from other workloads and objects in vCenter Server. The Linux kernel is based on Photon OS.
  • 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.
vSphere Pods are Open Container Initiative (OCI) compatible and can run containers from any operating system as long as these containers are also OCI compatible.
Figure 2. vSphere Pods Networking and Storage
vSphere Native Pods
vSphere Pods use three types of storage depending on the objects that are stored, that are ephemeral VMDKs, persistent volume VMDKs, and containers image VMDKs. As a vSphere administrator you configure storage policies for placement of container image cache, ephemeral VMDKs, and Kubernetes control plane VMs on the Supervisor Cluster level. On a namespace Supervisor Namespace level, you configure storage policies for placement of persistent volumes and for placement of the VMs of Tanzu Kubernetes clusters. See Storage in vSphere with Kubernetes for details about the storage requirements and concepts with vSphere with Kubernetes.

3

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 Networking in vSphere with Kubernetes