The Cloud Native Storage for vSphere with Tanzu workflow is as follows:
1. A developer deploys a pod using the kubectl CLI.
2. The vSphere with Tanzu Cloud Native Storage-Container Storage Interface (CNS-CSI) reads this request from the control plane API server.
3. CNS-CSI informs the vCenter Server CNS of the need for a disk with storage class Gold.
4. CNS interfaces with SPBM for a suitable datastore that satisfies the Gold storage class (storage policy).
5. SPBM decides on a suitable datastore and interfaces with DRS for a suitable ESXi host.
6. Hostd on the ESXi host creates a First Class Disk (VMDK) on the datastore.
7. Spherelet on the ESXi host takes the created VMDK.
8. Spherelet mounts the VMDK to the vSphere Pod.
9. Spherelet reports the mount as a successful event to the control plane API server.

The container network interfaces (CNIs) supported with Tanzu Kubernetes clusters created by the Tanzu Kubernetes Grid Service are NSX-T and Antrea. NSX-T is a multi-cloud networking and security platform from VMware that provides built-in container networking and security capabilities. Antrea is an open-source CNI project created by the GitHub team that provides network policy enforcement for Kubernetes clusters. Both of these CNIs provide support for multi-tenancy and advanced network policy enforcement.

kubectl get tanzukubernetesreleases
List available Tanzu Kubernetes releases.
kubectl get tkr
Short form version of the preceding command.
kubectl get tkr v1.17.8---vmware.1-tkg.1.5417466 -o yaml
Provides details on the named Tanzu Kubernetes release.
VMware Tanzu distributes Kubernetes software versions as Tanzu Kubernetes releases. To consume these releases, you configure a vSphere Content Library and synchronize the available releases. You can do so using a subscription-based model, or on-demand. If you want to provision Tanzu Kubernetes in an internet restricted environment, you can create a local library and manually import the releases.