5V0-23.20 Practice Exam Questions with Answers VMware vSphere with Tanzu Specialist Certification

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.

Graphical user interface, Teams Description automatically generated

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.

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.

The storage policy would become a storage class in Kubernetes.

For some parts of your application (for example, frontends) you may want to expose a Service onto an external IP address, that's outside of your cluster.

Kubernetes ServiceTypes allow you to specify what kind of Service you want. The default is ClusterIP.

The Cloud Native Storage server resides in vCenter Server:

• Provisions and manages life cycle operations for container volumes

• Creates First Class Disks (FCDs) to support the container volumes

• First Class Disks exist as .vmdk and -flat.vmdk files on a vSphere datastore •

Integrates with storage policy based management (SPBM) for the placement of disks

A First Class Disk (FCD) is also called an improved virtual disk. It is a named virtual disk that is unassociated with a VM. These disks reside on a VMFS, NFS, or vSAN datastore and support container volumes.

Storage policy based management (SPBM) is a vCenter Server service that supports provisioning of persistent volumes according to specified storage requirements. After provisioning, the service monitors compliance of the volume with the required policy characteristics.

A virtual machine class is a request for resource reservations for processing power on the virtual machine (VM), including CPU and memory (RAM). For example, the VM class type named "guaranteed-large" reserves 4 CPU and 16 GB RAM. See Default Virtual Machine Classes for a list of default VM classes and their corresponding CPU and RAM reservations.

The VM disk size is set by the OVA template, not the VM class definition. For Tanzu Kubernetes releases, the disk size is 16GB. See About Tanzu Kubernetes release Distributions.

There are two reservation types for VM classes: guaranteed and best effort. The guaranteed class fully reserves its configured resources. This means that for a given cluster the spec.policies.resources.requests matches the spec.hardware settings. The best effort class allows resources to be overcommitted. For production workloads it is recommended that you use the guaranteed VM class type.

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.

https://docs.docker.com/docker-hub/repos/

Graphical user interface, text, application Description automatically generated

• Registry Service: Developers can store and manage Docker and OCI images using Harbor. Harbor is an open-source container image registry that secures images with role-based access control.

Procedure

• Login to Harbor Registry with the vSphere Docker Credential Helper.

Note:While providing --user username is acceptable for login, you should use the UserPrincipalName (UPN) syntax ( --user username@domain.com) to login and use docker push commands.

• Tag the image that you want to push to the project in Harbor Registry with same name as the namespace, where you want to use it:

For example:

• uk.co.certification.simulator.questionpool.PList@77298960
• To push an image to a project in Harbor, run the following command:Syntax:

For example:

• uk.co.certification.simulator.questionpool.PList@77298ab0

Expected result.

• uk.co.certification.simulator.questionpool.PList@77298b00

Virtual Machine Class Types for Tanzu Kubernetes Clusters

A virtual machine class defines the resource sizing for Tanzu Kubernetes cluster VMs: • CPU • Memory •

Storage

Virtual machine class types range from extra small (xsmall) to extra large (xlarge). Class types are categorized as guaranteed or best effort:

• Guaranteed: Reserve all CPU and memory allocations. • Best effort: Allocate the same CPU and memory but do not reserve the resources.

The class type guaranteed-small allocates 2 CPU, 4 GB of memory, and 16 GB of storage and reserves CPU and memory allocations. Custom virtual machine class types cannot be defined.

• Create an example pod spec with the details about the private registry.

vSphere Pods are only supported on Supervisor Clusters that use NSX-T Data Center as their networking stack.

Resource Management. vSphere DRS handles the placement of vSphere Pods on the Supervisor Cluster.

Print the client and server version information.

Synopsis

Print the client and server version information.

• kubectl version

https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-702-vsphere-with-tanzu-guide.pdf

Configuring Workload Networks You configure one or more workload networks and their respective IP address ranges.

Each workload network is assigned a vSphere Distributed Switch port group and uses a defined IP range to allocate IP addresses to workloads (VMware Tanzu Kubernetes clusters).

Enabling Harbor Image Registry

The vSphere administrator uses the vSphere Client to enable Harbor. To enable this component, select a cluster, select Configure > Namespaces > Image Registry, and click ENABLE HARBOR:

• A VM Storage Policy is required to allocate storage for the Harbor pods.

• An IP Address, based on the ingress CIDR range, is allocated for the Harbor management interface.

• After a few minutes, Harbor is deployed and running. 184

• The HAProxy virtual IP range where external services and DevOps users connect. In this configuration, HAProxy is deployed with two virtual NICs (Default configuration), one connected to the management network, and a second one connected to the Primary Workload Network. You must plan for allocating Virtual IPs on a separate subnet from the Primary Workload Network.

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-1F885AAE-92FF-41E6-BF04-0F0FD4173BD9.html