5V0-23.20 Questions and Answers

Fetch all Pods in all namespaces using kubectl get pods --all-namespaces

Pods

Shortcode = po

List one or more pods

• kubectl get pod

Delete a pod

• kubectl delete pod

Display the detailed state of a pods

• kubectl describe pod

Create a pod

• kubectl create pod

Execute a command against a container in a pod

• kubectl exec -c <container_name>

Get interactive shell on a a single-container pod

• kubectl exec -it /bin/sh

Display Resource usage (CPU/Memory/Storage) for pods

• kubectl top pod

Add or update the annotations of a pod

• kubectl annotate pod

Add or update the label of a pod

• kubectl label pod

The Network Service has been extended to support the vSphere Distributed Switch (vDS). Start by configuring the switch with appropriate portgroups. Management will carry traffic between vCenter and the Kubernetes Control Plane (Supervisor Cluster control plane). As we will see in a moment, not having the built in Load Balancing capability of NSX means you will need to deploy your own load balancer externally from the cluster. We will give you a choice of integrated load balancers. The first one we support is HAProxy.

The Management network will also carry traffic between the supervisor cluster nodes and HAProxy. The Frontend network will carry traffic to the Load Balancer virtual interfaces. It must be routable from any device that will be a client for your cluster. Developers will use this to issue kubectl commands to the Supervisor cluster or their TKG clusters. You can have one or more Workload networks.

The primary Workload network will connect the cluster interfaces of the Supervisor cluster. Namespaces can be defined with their own Workload network allowing for isolation between development teams assigned different Namespaces. The Namespace assigned Workload Networks will connect the TKG cluster nodes in that Namespace.

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

For example:

• uk.co.certification.simulator.questionpool.PList@1dd10d20

Expected result.

• uk.co.certification.simulator.questionpool.PList@1dd10d60

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.

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.

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.