DELL APEX Cloud Platform for Red Hat OpenShift: How to switch external registry

Prerequisites

• You have successfully set up a new external registry and it is now ready for use.

Procedure

1. Edit the global pull-secret secret (namespace: openshift-config) to add the credential of new registry. Refer to the OpenShift documentation Updating the global cluster pull secret for detailed instructions.
   e.g.
2. (Optional) If the old registry is no longer in use, you can remove its associated credentials from this page.
3. Configure the registry for container image access.
   1. If your registry configuration uses HTTPS, prepare the root CA certificate of the registry as a PEM format file. Then, add the registry's root CA certificate to the OCP cluster by editing the existing acp-ingress-ca config map resource in the openshift-config namespace.
      e.g.
       
   2. If your registry configuration uses HTTP, add it to the insecure registries list in the global Image configuration.
      e.g.
       
4. (Optional) If the old registry is no longer in use, you can remove its associated items from the same pages.

5. To update images from Depot Manager to the new external registry, follow these steps:

   1. Refer to the Dell APEX Cloud Platform for Red Hat OpenShift Administrator Guide and perform the procedure of "Update Images from the Depot Manager to the External Registry".
      Note: The --registry (or -r) option is required and must be specified.

   2. Once the images are updated, verify that they can be pulled from the external registry by following the procedure of "Verify pull ocp-v4.0-art-dev from the external registry for cluster power outage, shutdown, and reboot".
6. (Optional) For the systems with restricted network access, you need switch the registry for OperatorHub.
   1. Refer to the Dell APEX Cloud Platform for Red Hat OpenShift Deployment Guide and follow the procedure of "Configure the OperatorHub on a restricted network system".