As a vSphere administrator, you can enable a private image registry on the Supervisor Cluster through the Registry Service. DevOps engineers can push and pull images from the registry as well as deploy vSphere Pods by using these images. The Registry Service is only supported with vSphere Pods and therefore it is available for Supervisor Clusters that are configured with NSX-T Data Center as the networking stack.
- Create a storage policy for placement of container images.
- In the vSphere Client, browse to the cluster where you want to enable the image registry.
- Select Configure.
- Under Namespaces, select Image Registry.
- Click Enable Harbor.
- Select the storage policy for placement of container images.
A private image registry becomes enabled after a few minutes. A special namespace is created for that instance of the private image registry. You cannot perform any operations on that namespace, it is read only for vSphere users.
Every namespace on the Supervisor Cluster has a matching project with the same name as the private image registry. Every user or group that has edit or view permission to a namespace becomes a corresponding role member on the matching project with the same name in the private image registry. The lifecycle of projects and members of the private image registry is automatically managed and is linked to the lifecycle of namespaces and user or group permissions in namespaces.
What to do next
Provide the URL of the private image registry instance to the DevOps engineers.