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

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.

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

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.

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/

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.