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

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.

• kubectl get tanzukubernetesreleases

List available Tanzu Kubernetes releases.

• kubectl get tkr

Short form version of the preceding command.

• kubectl get tkr v1.17.8---vmware.1-tkg.1.5417466 -o yaml

Provides details on the named Tanzu Kubernetes release.

VMware Tanzu distributes Kubernetes software versions as Tanzu Kubernetes releases. To consume these releases, you configure a vSphere Content Library and synchronize the available releases. You can do so using a subscription-based model, or on-demand. If you want to provision Tanzu Kubernetes in an internet restricted environment, you can create a local library and manually import the releases.

Text Description automatically generated

Creating a Namespace

A vSphere administrator configures permissions and storage before a namespace can be used:

• Assign edit or view permissions to users. Users must be present in a configured single sign-on (SSO) identity source.

• Must assign a VM storage policy to the namespace.

• Can define resource limits (optional).

• Must add a content library to enable the Tanzu Kubernetes Grid Service.

Tanzu Kubernetes Cluster is a Kubernetes cluster deployed by developers using a YAML specification file. It uses resources from hosts across vSphere clusters to form a Kubernetes cluster on vSphere. It also enables vSphere High Availability and Distributed Resource Scheduler, which allows for load balancing and high availability of resources in the cluster. It does not remove the Kubernetes API for use by DevOps teams.

Graphical user interface Description automatically generated

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

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.

A Supervisor Cluster namespace is a combination of resource allocations and permissions set within the Supervisor Cluster. When you create a Supervisor Namespace, you’ll assign who has access to use it, and how many of the ESXi cluster’s resources you can use (much like a resource pool).

When you enabled the Workload Management components, you created a special Kubernetes cluster called the “Supervisor Cluster”. You can continue to deploy virtual machines in this cluster, and you can also deploy kubernetes pods as a “pod vm” which is basically a container with some special wrapping so they are better isolated, like a virtual machine is.

The storage policy would become a storage class in Kubernetes.

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@d8e88b0
• To push an image to a project in Harbor, run the following command:Syntax:

For example:

• uk.co.certification.simulator.questionpool.PList@d8e8960

Expected result.

• uk.co.certification.simulator.questionpool.PList@d8e89b0

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.