5.2. Accessing registry directly from the cluster

You can access the registry from inside the cluster.

Procedure

Access the registry from the cluster by using internal routes:

Access the node by getting the node’s address:
```
$ oc get nodes
```
```
$ oc debug nodes/<node_address>
```
To enable access to tools such as oc and podman on the node, run the following command:
```
sh-4.2# chroot /host
```
Log in to the container image registry by using your access token:
```
sh-4.2# oc login -u kubeadmin -p <password_from_install_log> https://api-int.<cluster_name>.<base_domain>:6443
```
```
sh-4.2# podman login -u kubeadmin -p $(oc whoami -t) image-registry.openshift-image-registry.svc:5000
```
You should see a message confirming login, such as:
```
Login Succeeded!
```
注意
You can pass any value for the user name; the token contains all necessary information. Passing a user name that contains colons will result in a login failure.
Since the Image Registry Operator creates the route, it will likely be similar to default-route-openshift-image-registry.<cluster_name>.

Perform podman pull and podman push operations against your registry:

重要

You can pull arbitrary images, but if you have the system:registry role added, you can only push images to the registry in your project.

In the following examples, use:

Push the newly tagged image to your registry:

$ podman push image-registry.openshift-image-registry.svc:5000/openshift/image