5V0-23.20 VMware vSphere with Tanzu Specialist Question and Answers

Graphical user interface, application Description automatically generated

Permissions for programmers should be assign at the Namespace level, typically using groups and roles.

You assign roles for the Namespace to Active Directory groups. You can later assign access to users by adding them to these groups. You assign access to separate Active Directory groups for the edit and view roles in the Namespace.

A user can have permissions on multiple namespaces. The kubectl commands are typically actioned against the current active namespace.

View the list of available namespaces:

kubectl config get-contexts

Change the current active namespace:

kubectl config use-context

A ReplicaSet declares how the functionality of a pod is made scalable and resilient through redundancy. The ReplicaSet ensures that a specified number of pods is kept running. Example: Deploy a ReplicaSet. • The ReplicaSet name is nginx-replica-demo. • Two replicas are expected to be running. • The ReplicaSet applies to pods with label nginx.

For more information about Kubernetes replica sets, see https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/

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.

The Workload Network, such as TKGS-VLAN1000, is where the Tanzu Kubernetes clusters run.

A workload network is a network construct that is used by supervisor control plane VMs and vSphere namespaces:

• The workload network is supported by a vSphere Distributed Switch port group.

• An IP range is defined to allocate an IP address for VMs attached to the workload network.

• A primary workload network must be selected.

• The supervisor control plane VMs attach to the primary workload networks port group.

A workload network can be used by multiple namespaces. A namespace can be assigned only one workload network.

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.

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

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.

Deleting Artifact:

When an artifact is not referenced by any OCI index, you can delete the artifact freely which will delete its manifest and all associated tags.

When an artifact is referenced by an OCI index, you cannot delete it. In order to delete this artifact, you must first delete all OCI indexes referencing this artifact first, remembering that an artifact can be referenced by multiple parents artifacts pushed onto Harbor by different users. So when deleting an OCI index holding 9 children artifacts not referenced by any other index and 1 child artifact referenced by another index, only 9 out of 10 children artifacts will be deleted.

To delete any artifact in the Harbor interface, click on the artifact and select ‘Delete’ and confirm.

Not Purge:As a vSphere administrator, you can purge the images for a project in the private image registry by request from DevOps engineers. Purging images from the private image registry deletes all references to the images made by pods, but it does not remove the images from the image registry.