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

External HTTP(S) Load Balancing is a proxy-based Layer 7 load balancer that enables you to run andscale your services behind a single external IP address.

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

From the vSphere Client menu, select Workload Management.

Select the Updates tab.

Select the Available Version that you want to update to.

For example, select the version v1.17.4-vsc0.0.2-16293900.

Select the Supervisor Cluster to apply the update to.

To initiate the update, click Apply Updates.

Use the Recent Tasks pane to monitor the status of the update.

Deleting Artifact:

When an artifact is not referenced by any OCI index, you can delete the artifact freely which will delete its manifest and all associated tags.

When an artifact is referenced by an OCI index, you cannot delete it. In order to delete this artifact, you must first delete all OCI indexes referencing this artifact first, remembering that an artifact can be referenced by multiple parents artifacts pushed onto Harbor by different users. So when deleting an OCI index holding 9 children artifacts not referenced by any other index and 1 child artifact referenced by another index, only 9 out of 10 children artifacts will be deleted.

To delete any artifact in the Harbor interface, click on the artifact and select ‘Delete’ and confirm.

Not Purge:

As a vSphere administrator, you can purge the images for a project in the private image registry by request from DevOps engineers. Purging images from the private image registry deletes all references to the images made by pods, but it does not remove the images from the image registry.

Creating a Namespace

A vSphere administrator configures permissions and storage before a namespace can be used:

• Assign edit or view permissions to users. Users must be present in a configured single sign-on (SSO) identity source.

• Must assign a VM storage policy to the namespace.

• Can define resource limits (optional).

• Must add a content library to enable the Tanzu Kubernetes Grid Service.

If you want to control traffic flow at the IP address or port level (OSI layer 3 or 4), then you might consider using Kubernetes NetworkPolicies for particular applications in your cluster.

NetworkPolicies are an application-centric construct which allow you to specify how a pod is allowed to communicate with various network "entities" (we use the word "entity" here to avoid overloading the more common terms such as "endpoints" and "services", which have specific Kubernetes connotations) over the network. NetworkPolicies apply to a connection with a pod on one or both ends, and are not relevant to other connections.

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.

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 commandline tool uses parameters from the current context to communicate with the cluster.

To choose the current context: kubectl config use-context ctx001