Downloading Container Image

IBM Sterling Control Center Container images can be either pulled directly from the IBM Entitled Registry into the cluster or copied to a private registry (such as OpenShift private registry) in the case of an air-gapped environment.

The following Container images are available for download from the IBM Entitled Registry:
cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18

Online cluster having access to IBM Entitled Registry

Create the entitled registry secret by following these steps:
  1. Ensure that you have obtained the entitlement key that is assigned to your ID.
    1. Log in to My IBM Container Software Library using the IBM ID and password associated with the entitled software. If you are not directed to the entitlement page, click Get an entitlement key and obtain the Entitlement Key.
    2. In the Entitlement keys section, select Copy key to copy the entitlement key to the clipboard.
    3. Save the entitlement key to a safe location for later use.
    4. To confirm the validity of your entitlement key, click View library on the left side of the page.
    5. Check the list of products to verify your entitlement. If IBM Sterling Control Center Monitor is not listed or if the View library link is disabled, it indicates that the logged-in identity lacks entitlement for IBM Sterling Control Center. In such a case, the entitlement key is not valid for the software installation.
  2. Configure the entitled registry information by following these steps:

    1. export ENTITLED_REGISTRY=cp.icr.io

    2. export ENTITLED_REGISTRY_USER=cp
    3. export ENTITLED_REGISTRY_KEY=<entitlement_key>
  3. Create a Docker-registry secret:
    oc create secret docker-registry sccm-image-secret --docker-username=$ENTITLED_REGISTRY_USER --docker-password=$ENTITLED_REGISTRY_KEY --docker-email=<your_docker_email_address> --docker-server=$ENTITLED_REGISTRY -n ibm-sccm

This image pull secret will be utilized in the configuration for pulling the IBM Control Center image.

Air Gap Cluster

Log in to a Linux system that fulfills the following prerequisites:
  • Have docker or podman installed
  • Have access to entitlement registry
  • Have access to OpenShift or a local image registry
Execute these steps to download and push images to an OpenShift or a local image registry.
  1. Log in to the IBM Entitled Registry using the credentials obtained in the previous Online cluster having access to IBM Entitled Registry section.
    $ docker login cp.icr.io -u cp -p <entitlement_key>

$ podman login cp.icr.io -u cp -p <entitlement_key>
  2. Download the image using the docker or podman pull command.
    $ docker pull cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18

$ podman pull cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18
  3. Tag the downloaded image with the correct local or OpenShift registry.
    $ docker tag cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18 <registry URL>:<tag>

$ podman tag cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18 <registry URL>:<tag>
    For example:
    $ docker tag cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18 my-registry/my-namespace/ibmscc:6.3.1.0_iFix01_2024-02-01
$ podman tag cp.icr.io/cp/ibm-scc/ibmscc:6.3.1.0.iFix04_2025-03-18 my-registry/my-namespace/ibmscc:6.3.1.0_iFix01_2024-02-01
  4. Login to OpenShift or a local image registry.
    $ docker login <registry URL> -u <registry user> -p <registry user’s password>

$ podman login <registry URL> -u <registry user> -p <registry user’s password>
  5. Push the Docker image using the docker or podman push command.
    $ docker push <registry URL>:<tag>

$ podman push <registry URL>:<tag>
    For example:
    $ docker push my-registry/my-namespace/ibmscc:6.3.1.0.iFix04_2025-03-18

$ podman push my-registry/my-namespace/ibmscc:6.3.1.0.iFix04_2025-03-18
  6. Now, create a Docker-registry secret in the cluster for pulling images from OpenShift or a local image registry:
    $ oc create secret docker-registry sccm-image-secret --docker-username=<registry user> --docker-password=<registry user’s password> --docker-email=<your_docker_email_address> --docker-server=<registry URL> -n ibm-sccm

Now, the image pull secret sccm-image-secret has been created, whether the image will be pulled from the IBM Entitled Registry or from OpenShift or a local image registry.

If you are using the default service account or any pre-existing service account, add the image pull secret using the following command:

oc patch serviceaccount <service-account-name> -p '{"imagePullSecrets": [{"name": "<pull-secret-name>"}]}'

Example:

oc patch serviceaccount default -p '{"imagePullSecrets": [{"name": "sccm-image-secret"}]}'