accessing-the-registry.adoc

Accessing the registry

Use the following sections for instructions on accessing the registry, including viewing logs and metrics, as well as securing and exposing the registry.

You can access the registry directly to invoke podman commands. This allows you to push images to or pull them from the integrated registry directly using operations like podman push or podman pull. To do so, you must be logged in to the registry using the podman login command. The operations you can perform depend on your user permissions, as described in the following sections.

Prerequisites

• You have access to the cluster as a user with the cluster-admin role.

• You must have configured an identity provider (IDP).

• For pulling images, for example when using the podman pull command, the user must have the registry-viewer role. To add this role, run the following command:

  $ oc policy add-role-to-user registry-viewer <user_name>

• For writing or pushing images, for example when using the podman push command:

  • The user must have the registry-editor role. To add this role, run the following command:

    $ oc policy add-role-to-user registry-editor <user_name>

  • Your cluster must have an existing project where the images can be pushed to.

modules/registry-accessing-directly.adoc

modules/registry-checking-the-status-of-registry-pods.adoc

modules/registry-viewing-logs.adoc

modules/registry-accessing-metrics.adoc

Additional resources

• For more information on allowing pods in a project to reference images in another project, see Allowing pods to reference images across projects.

• A kubeadmin can access the registry until deleted. See Removing the kubeadmin user for more information.

• For more information on configuring an identity provider, see Understanding identity provider configuration.