Skip to content

Bind a registry space to workspace

There are two types of registry spaces: public and private. Images in the public registry space are public images, and images in the private registry space are private images.

For public images, when deploying applications in the container management module, users can click the Select Image button to select container registry - registry Integration in all the images in the public registry space to deploy applications without any configuration.

For a private image, the administrator must allocate the private registry space to the workspace (tenant) before it can be used by members under the workspace to ensure the security of the private image.

Prerequisite: An external Harbor registry has been created or integrated, and one or more registry spaces have been created.

Binding steps

  1. Log in to the web console as a user with the Admin role, and click container registry from the left navigation bar.

  2. Click registry Integration on the left navigation bar, click a registry name to enter the registry, and navigate to the displayed registry Space menu.

  3. Click the Bind Workspace button on the right side of a registry space entry, and select the workspace to be bound.

  4. Click OK to finish binding the workspace.

FAQ

  1. When deploying an application in the Kubernetes namespace, the image in the registry space cannot be selected through the "Select Image" button.

    • Check whether the Kubernetes namespace is bound to a workspace (binding is required).
    • Check whether the registry space is bound to the workspace where the Kubernetes namespace is located (binding is required).
    • To check whether the status of the registry space is private or public, switch to the following tab to find out.

  2. What is the difference between assigning a registry space to a workspace and associating a registry under a workspace?

    The platform administrator Admin can manage in a unified manner, and assign a registry space to multiple workspaces in batches without having to associate them separately.

    Workspace Admin Workspace Admin can associate external container registrys for members to use according to needs, without relying on platform administrators, which is more flexible to use.

Comments