Setting up the private registry

Edit online

A private image registry must be used to store all images in your local environment. Create a registry and make sure that it meets the requirements. It must be available and accessible from the OpenShift® Container Platform cluster nodes.

Before you begin

The steps in the Procedure section must be run in your private registry and not on the OpenShift Container Platform cluster that is used for the Cloud Pak for Business Automation deployment. Examples of private registries are Sonotype Nexus repository and JFrog Artifactory.

About this task

Make sure that your image registry meets the following requirements:

  • Supports Docker Manifest V2, Schema 2.
  • Supports multi-architecture images.
    Note: Do not use the Red Hat OpenShift image registry as your private registry. The Red Hat OpenShift registry does not support multi-architecture images.
  • Is accessible from both the host and your OpenShift Container Platform cluster nodes.
  • Has the username and password of a user who can write to the target registry from the host.
  • Has the username and password of a user who can read from the target registry that is on the OpenShift Container Platform cluster nodes.
  • Allows path separators in the image name.

Procedure

  1. Create a cp namespace to store the images in the IBM Entitled Registry cp.icr.io/cp.

    The cp namespace needs an entitlement key and credentials to pull the images. The namespace must have a user who can write and create repositories, and read all repositories.

  2. Create a ibmcom namespace to store all images for all IBM images that do not require credentials to pull.
  3. Create a cpopen namespace to store all images from the icr.io/cpopen repository.

    The cpopen namespace is for publicly available images that are hosted by IBM that do not require credentials to pull.

  4. Create a opencloudio namespace to store the images from quay.io/opencloudio.

    The opencloudio namespace is for select IBM open source component images that are available on quay.io. The IBM Cloud® Platform Common Services images are hosted on opencloudio.

What to do next

Important: Verify that each namespace meets the following requirements:
  • Supports auto-repository creation.
  • Has credentials of a user who can write and create repositories. The host uses these credentials.
  • Has credentials of a user who can read all repositories. The OpenShift Container Platform cluster uses these credentials.

You can now set up the image inventory. For more information, see Setting up the CASE archive and inventory.