Drive it with your mouse, your finger, or just use the arrow keys.
Use Learn mode to learn the demo. The orange boxes show where to click.
Use Present mode to hide the orange boxes and notes.
Click a Shortcut to jump to a specific part of the demo.
VMware Cloud Foundation
Enabling the Harbor Registry for vSphere with Kubernetes
Welcome to this demonstration on enabling the Harbor Registry with vSphere with Kubernetes on VMware Cloud Foundation.
As a vSphere administrator, you can enable a private image registry on the vSphere with Kubernetes Supervisor Cluster by deploying the Registry Service. Once deployed, developers can push and pull images from the registry as well as deploy vSphere Pods using these images.
This demonstration shows the steps to enable the Harbor Registry service on a workload domain where vSphere with Kubernetes has been enabled.
Prior to enabling the Harbor Registry you need to have completed the following tasks:
Enabling the Harbor Registry is done by the IT Operator using the vSphere Web Client.
Here we see a three-node vSphere cluster that was deployed by VMware Cloud Foundation as part of the “wld01” domain. Note that we can tell that vSphere with Kubernetes has been enabled on this cluster as we see the three supervisor nodes that make up the vSphere pod service.
To enable the Harbor Registry we need to go to the cluster settings.
Under the Image Registry we see the “Enable Harbor” button.
The Harbor Registry will be deployed as a set of containers on the vSphere Pod Service. Prior to deploying the containers we need to select the vSAN storage policy to use.
That’s it! The vSphere Web Client talks to the control plane on the vSphere Pod Service to deploy the Harbor Registry. It will typically take less than 10 minutes to deploy the Harbor Registry.
Under Namespaces we see a new object has been created called “vmware-system-registry-1…”.
We see the Harbor containers that make up the Harbor Registry.
On the cluster configuration page we see the health of the registry shown as “Running” along with a summary of the storage used and a link to the UI where we can login and manage the images in the registry.
This concludes the demonstration on enabling the Harbor Registry.
As a vSphere administrator, you can enable a private image registry on the Supervisor Cluster where vSphere with Kubernetes has been enabled by deploying the Registry Service. Once deployed, developers can push and pull images from the registry as well as deploy vSphere Pods by using these images.
Follow along by completing the next demonstration showing how to create a namespace and how to enable developer access to vSphere with Kubernetes.
For more information on VMware Cloud Foundation, visit our website at vmware.com/go/cloudfoundation.