Downloading the Container Software for Online Cluster

The cluster which has access to the internet is called Online cluster. You may have a Kubernetes or OpenShift cluster and it has access to the internet.

Create the entitled registry secret:
Complete the following steps to create a secret with the entitled registry key value:
1. Ensure that you have obtained the entitlement key that is assigned to your ID.
  1. Log in to My IBM Container Software Library by using the IBM ID and password that are associated with the entitled software. In case, 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.
    
    To conﬁrm that your entitlement key is valid, click View library that is provided in the left of the page. You can view the list of products that you are entitled to. If IBM Sterling Control Center Monitor is not listed, or if the View library link is disabled, it indicates that the identity with which you are logged in to the container library does not have an entitlement for IBM Sterling Control Center. In this case, the entitlement key is not valid for installing the software.
2. Set the entitled registry information by completing the following steps:
  1. export ENTITLED_REGISTRY=cp.icr.io
  2. export ENTITLED_REGISTRY_USER=cp
  3. export ENTITLED_REGISTRY_KEY=<entitlement_key>

Create a Docker-registry secret:

$ oc create secret docker-registry sccm-image-secret --
dockerusername=$ENTITLED_REGISTRY_USER --docker-password=$ENTITLED_REGISTRY_KEY --
dockeremail=<your_docker_email_address> --docker-server=$ENTITLED_REGISTRY -n ibm-sccm

Configure the pull secret in the service account used for deployment by running 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"}]}

Tip: It is recommended to configure the pull secret in the service account, as it automatically binds as a pull secret for all application pods. If the pull secret is added to the service account, the image.imageSecrets configuration in the Helm configuration file is not required.