VMware 5V0-23.20 VMware vSphere with Tanzu Specialist Exam Practice Test

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.

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.

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.

NSX Container Plugin (NCP) runs as a pod on the control plane VMs. It listens for requests for network objects to the API server and interfaces with the NSX Manager to create, update, or delete those objects:

• A request to create a namespace results in a new NSX segment.

• A request to deploy a pod results in a segment port request and IP assignment.

• A request to create a service results in a new virtual server.

• A request to create a network policy results in a new distributed firewall rule.

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

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.