Download VMware vSphere with Tanzu Specialist.VCEPlus.5V0-23.20.2022-09-14.1e.64q.vcex

The vSphere administrator defines and assigns VM storage policies to a namespace:
VM storage policies are translated into Kubernetes storage classes.
Developers can access all assigned VM storage policies in the form of storage classes.
Developers cannot manage storage classes.
Storage class names are created in the following way:
Spaces in VM Storage Policy names are replaced with hyphens (-).
Special characters are replaced with a digit. A VM Storage Policy called My Gold Policy $ is called my-gold-policy-0 as a storage class.

  
 
Spherelet is a kubelet that is ported natively to ESXi. It allows the ESXi host to become part of a Kubernetes cluster. Spherelet performs the following functions:
Communicates with the control plane VMs
Manages node configuration
Starts vSphere Pods
Monitors vSphere Pods

  
 
A vSphere Pod is a VM with a small footprint that runs one or more Linux containers. With vSphere Pods, workloads have the following capabilities:
Strong isolation from a Linux kernel based on Photon OS
Resource management using DRS
Same level of resource isolation as VMs
Open Container Initiative (OCI) compatible
Equivalent to a Kubernetes Container Host vSphere Pods are not compatible with vSphere vMotion. When an ESXi host is placed into maintenance mode, running vSphere Pods are drained and redeployed on another ESXi host, but
only if the vSphere Pod is part of a ReplicaSet.

  
 
VMware Tanzu Mission ControlTM is a centralized management platform for consistently operating and securing your Kubernetes infrastructure and modern applications across multiple teams and clouds.

To connect to the Supervisor Cluster, run the following command. kubectl vsphere login --server=SUPERVISOR-CLUSTER-CONTROL-PLANE-IP --tanzu-kubernetes-cluster-name TANZU-KUBERNETES-CLUSTER-NAME --tanzu-kubernetes-cluster-namespace SUPERVISOR-NAMESPACE-WHERE-THE-CLUSTER-ISDEPLOYED --vsphere-username VCENTER-SSO-USER-NAME For example: kubectl vsphere login --server=10.92.42.137 --tanzu-kubernetes-cluster-name tanzu-kubernetes-cluster-01 --tanzu-kubernetes-cluster-namespace tanzu-ns-1 --vsphere-username [email protected]

Scale a Cluster Horizontally With the Tanzu CLI
To horizontally scale a Tanzu Kubernetes cluster, use the tanzu cluster scale command. You change the number of control plane nodes by specifying the --controlplane-machine-count option. You change the number of worker nodes by specifying the --worker-machine-count option.

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-A7756D67-0B95-447D-A645-E2A384BF8135.html
A Tanzu Kubernetes cluster provisioned by the Tanzu Kubernetes Grid Service supports two CNI options: Antrea (default) and Calico. Both are open-source software that provide networking for cluster pods, services, and ingress.
Tanzu Kubernetes clusters provisioned by the Tanzu Kubernetes Grid Service support the following Container Network Interface (CNI) options:
Antrea
Calico
  

Tanzu Kubernetes Grid Service CNI
Tanzu Kubernetes Grid Service supports Antrea and Calico as container network interfaces (CNI).
The default CNI in vSphere 7 Update 1 is Antrea.
Antrea is a VMware-supported, open source, Kubernetes-native project that implements the container network interface (CNI) and Kubernetes network policy, providing network connectivity and security for pod workloads. Antrea extends the benefit of programmable networks from Open vSwitch (OVS) to Kubernetes.
For more information about Antrea, see https://antrea.io/

The vSphere administrator configures a Subscribed Content Library on the Supervisor Cluster. The virtual machine image that is used for the Tanzu Kubernetes cluster nodes is pulled from this library.
A Subscribed Content Library originates from a Published Content Library. After the subscription is created, the system synchronizes it with the published library. To create the Tanzu Kubernetes cluster nodes, VMware publishes a Photon OS OVA library to which you subscribe. After the subscriber is synchronized with the publisher, you associate the content library with the Supervisor Cluster.

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.

Also, kubectl delete pvc, which is much shorter.
DevOps engineers create persistent volume claims to request persistent storage resources. The request provisions a persistent volume object and a matching virtual disk. In the vSphere Client, the persistent volume claim manifests as an FCD virtual disk that can be monitored by vSphere administrators.
The claim is bound to the persistent volume. The workloads can use the claim to mount the persistent volumes and access storage.
When the DevOps engineers delete the claim, the corresponding persistent volume object and the provisioned virtual disk are also deleted.