Certain Kubernetes workloads require persistent storage to store data permanently. To provision persistent storage for Kubernetes workloads, vSphere with Tanzu integrates with Cloud Native Storage (CNS), a vCenter Server component that manages persistent volumes.
Persistent storage is used by vSphere Pods, Tanzu Kubernetes clusters, and VMs. The following example illustrates how persistent storage is used by a vSphere Pod.
vSphere Pods use different types of storage depending on the objects that are stored. The types of storage are ephemeral virtual machine disks (VMDKs), persistent volume VMDKs, and containers image VMDKs:
* Storage policies for container image and ephemeral disks are defined at the cluster level.
* Storage policies for persistent volumes are defined at the namespace level.
* Networking for vSphere Pods uses the topology provided by NSX.

A Supervisor Cluster namespace is a combination of resource allocations and permissions set within the Supervisor Cluster. When you create a Supervisor Namespace, you'll assign who has access to use it, and how many of the ESXi cluster's resources you can use (much like a resource pool).
When you enabled the Workload Management components, you created a special Kubernetes cluster called the "Supervisor Cluster". You can continue to deploy virtual machines in this cluster, and you can also deploy kubernetes pods as a "pod vm" which is basically a container with some special wrapping so they are better isolated, like a virtual machine is.