VMware 5V0-23.20 Practice Test - Questions Answers, Page 5

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.

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.

Developers can list the available storage classes in their namespace by running the kubectl describe ns <namespace-name> command.

The storage policy would become a storage class in Kubernetes.

Create the ResourceQuota:

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

View detailed information about the ResourceQuota:

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

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.

Create an example pod spec with the details about the private registry.

apiVersion: v1

kind: Pod

metadata:

name: <workload-name>

namespace: <kubernetes-namespace>

spec:

containers:

- name: private-reg-container

image: <Registry-IP-Address>/<vsphere-namespace>/<image-name>:<version>

imagePullSecrets:

- name: <registry-secret-name>

Replace <workload-name> with the name of the pod workload.

Replace <kubernetes-namespace> with the Kubernetes namespace in the cluster where the pod will be created. This must be the same Kubernetes namespace where the Registry Service image pull secret is stored in the Tanzu Kubernetes cluster (such as the default namespace).

Replace <Registry-IP-Address> with the IP address for the embedded Harbor Registry instance running on the Supervisor Cluster.

Replace <vsphere-namespace> with the vSphere Namespace where the target Tanzu Kubernetes is provisioned.

Replace <image-name> with an image name of your choice.

Replace <version> with an appropriate version of the image, such as "latest".

Replace <registry-secret-name> with the name of the Registry Service image pull secret that you created previously.

VMware Harbor Registry

VMware Harbor Registry is an enterprise-class registry server that stores and distributes container images. Harbor allows you to store and manage images for use with VMware Tanzu Kubernetes Grid Integrated Edition (TKGI).

Overview

Harbor extends the open source Docker Distribution by adding the functionalities usually required by an enterprise, such as security, identity, and management. As an enterprise private registry, Harbor offers enhanced performance and security. Deploying a registry alongside the TKGI environment improves image management efficiency.