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

A context element in a kubeconfig file is used to group access parameters under a convenient name. Each context has three parameters: cluster, namespace, and user. By default, the kubectl command-line tool uses parameters from the current context to communicate with the cluster.

To choose the current context:

kubectl config use-context ctx001

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.

Explanation

VMware created Harbor in 2014. Harbor was shared with the community through an open-source license in 2016 and donated to the Cloud Native Computing Foundation (CNCF) in 2018.

Harbor is integrated into VMware products: vSphere Integrated Containers, Tanzu Kubernetes Grid Integrated Edition, and vSphere with Tanzu. The embedded Harbor for vSphere with Tanzu includes the following features: •

Identity integration and role-based access control

• Graphical user interface

• Auditing of operations

• Management with labels

Authenticating Using kubectl

In vSphere with Tanzu, authentication is performed using vCenter Single Sign-On. You run the command kubectl vsphere login to authenticate a user through vCenter Single Sign-On to Kubernetes clusters.

kubectl vsphere login --server -u

The --insecure-skip-tls-verify flag is required if the certificate presented by the vSphere with Tanzu control plane is not trusted by the client machine. The control plane is signed by the vCenter Server VMware CA by default. You can replace the control plane certificate with a trusted certificate if needed. Alternatively, install the vCenter Server VMware CA root certificate into your client machine to remove the need for the --insecure-skip-tls-verify flag.

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

Explanation

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/

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/

Be aware of the following constraints when upgrading your cluster.

You can upgrade a cluster up to one minor version of Kubernetes from its current version. If necessary, you can perform subsequent upgrades to move the version forward.

Upgrading your version of Kubernetes is a one-way operation. You cannot subsequently downgrade the Kubernetes version, or undo an upgrade.

Graphical user interface Description automatically generated

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.