Pass the VMware VMware Certified Specialist - vSphere with Tanzu 2022 5V0-23.20 Questions and answers with CertsForce

For a Supervisor Cluster that is configured with the vSphere networking stack, you can provide Layer 2 isolation for your Kubernetes workloads by creating Workload Networks and assigning them to namespaces. Workload Networks provide connectivity to Tanzu Kubernetes clusters in the namespace and are backed by distributed port groups on the switch that is connected to the hosts in the Supervisor Cluster.

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.

External HTTP(S) Load Balancing is a proxy-based Layer 7 load balancer that enables you to run and scale your services behind a single external IP address.

When vSphere with Tanzu converts storage policies that you assign to namespaces into Kubernetes storage classes, it changes all upper case letters into lower case and replaces spaces with dashes (-). To avoid confusion, use lower case and no spaces in the VM storage policy names.

Storage Policy Based Management is a vCenter Server service that supports provisioning of persistent volumes and their backing virtual disks according to storage requirements described in a storage policy.

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-IS-DEPLOYED

--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 administrator@example.com