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

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.

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.

• 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.

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.

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 container network interfaces (CNIs) supported with Tanzu Kubernetes clusters created by the Tanzu Kubernetes Grid Service are NSX-T and Antrea. NSX-T is a multi-cloud networking and security platform from VMware that provides built-in container networking and security capabilities. Antrea is an open-source CNI project created by the GitHub team that provides network policy enforcement for Kubernetes clusters. Both of these CNIs provide support for multi-tenancy and advanced network policy enforcement.

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 < kubernetes control plane > -u < username >

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.

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.

Print the client and server version information.

Synopsis

Print the client and server version information.

kubectl version

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

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

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.

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.

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.

A dedicated IP range for virtual IPs. The HAProxy VM must be the only owner of this virtual IP range. The range must not overlap with any IP range assigned to any Workload Network owned by any Supervisor Cluster.