VMware 5V0-23.20 Dumps

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

Create the ResourceQuota:

• kubectl apply -f https://k8s.io/examples/admin/resource/quota-mem-cpu.yaml --namespace=quota-mem-cpu-example

View detailed information about the ResourceQuota:

• kubectl get resourcequota mem-cpu-demo --namespace=quota-mem-cpu-example --output=yaml

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

Resource Name Description

configmaps The total number of ConfigMaps that can exist in the namespace.

persistentvolumeclaims The total number of PersistentVolumeClaims that can exist in the namespace.

pods The total number of Pods in a non-terminal state that can exist in the namespace. A pod is in a terminal state if .status.phase in (Failed, Succeeded) is true.

replicationcontrollers The total number of ReplicationControllers that can exist in the namespace.

resourcequotas The total number of ResourceQuotas that can exist in the namespace.

services The total number of Services that can exist in the namespace.

services.loadbalancers The total number of Services of type LoadBalancer that can exist in the namespace.

services.nodeports The total number of Services of type NodePort that can exist in the namespace.

secrets The total number of Secrets that can exist in the namespace.

Enabling Harbor Image Registry

The vSphere administrator uses the vSphere Client to enable Harbor. To enable this component, select a cluster, select Configure > Namespaces > Image Registry, and click ENABLE HARBOR:

• A VM Storage Policy is required to allocate storage for the Harbor pods.

• An IP Address, based on the ingress CIDR range, is allocated for the Harbor management interface.

• After a few minutes, Harbor is deployed and running. 184

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

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 Cloud Native Storage for vSphere with Tanzu workflow is as follows:

1. A developer deploys a pod using the kubectl CLI.

2. The vSphere with Tanzu Cloud Native Storage-Container Storage Interface (CNS-CSI) reads this request from the control plane API server.

3. CNS-CSI informs the vCenter Server CNS of the need for a disk with storage class Gold.

4. CNS interfaces with SPBM for a suitable datastore that satisfies the Gold storage class (storage policy).

5. SPBM decides on a suitable datastore and interfaces with DRS for a suitable ESXi host.

6. Hostd on the ESXi host creates a First Class Disk (VMDK) on the datastore.

7. Spherelet on the ESXi host takes the created VMDK.

8. Spherelet mounts the VMDK to the vSphere Pod.

9. Spherelet reports the mount as a successful event to the control plane API server.

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

• 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

• The HAProxy virtual IP range where external services and DevOps users connect. In this configuration, HAProxy is deployed with two virtual NICs (Default configuration), one connected to the management network, and a second one connected to the Primary Workload Network. You must plan for allocating Virtual IPs on a separate subnet from the Primary Workload Network.

Certain Kubernetes workloads require persistent storage to store data permanently. To provision persistent storage for Kubernetes workloads, vSphere with Tanzu integrates with Cloud Native Storage (CNS), a vCenter Server component that manages persistent volumes.

Persistent storage is used by vSphere Pods, Tanzu Kubernetes clusters, and VMs. The following example illustrates how persistent storage is used by a vSphere Pod.

vSphere Pods use different types of storage depending on the objects that are stored. The types of storage are ephemeral virtual machine disks (VMDKs), persistent volume VMDKs, and containers image VMDKs:

• Storage policies for container image and ephemeral disks are defined at the cluster level.

• Storage policies for persistent volumes are defined at the namespace level.

• Networking for vSphere Pods uses the topology provided by NSX.