Accessing Process Mining images
To access and pull the IBM Process Mining Images from the IBM Entitled Registry, you must obtain your unique Entitlement Key and create two secrets, ibm-entitlement-key
and ibm-registry
, containing your unique
Entitlement Key. You use the ibm-entitlement-key
secret name for the IBM Process Mining Operator and the ibm-registry
secret name for the Db2 Operator.
Note: The Entitlement Key is valid only for the releases starting from Operator Version 1.0.1.
Obtaining an Entitlement Key
Procedure
- Log in to My IBM using your IBMid and password.
- Navigate through Container Software Library > View Library > Get Entitlement Key to view or copy your unique Entitlement Key.
Note:
- To verify the validity of the key, you use a container tool such as Docker. On the command line, you type the following command and specify the username and password as given below to log in to the IBM Entitled Registry:
docker login cp.icr.io --username cp --password
myEntitlementKey
Where myEntitlementKey
stands for your unique Entitlement Key.
Adding an Entitlement Key to a namespace
You use standard Kubernetes tools to create a pull secret (which contains your Entitlement Key) in all the namespaces where you install the {{site.data.keyword.pm_notm}} components. For the {{site.data.keyword.pm_notm}} Operators, you create a Docker Registry using the following command to add an Entitlement Key to a namespace:
oc create secret docker-registry ibm-entitlement-key \
--docker-username=cp \
--docker-password=myEntitlementKey \
--docker-server=cp.icr.io \
--namespace=myNamespace
Where ibm-entitlement-key
is the secret name, cp
is the username, and myEntitlementKey
is the password that stands for your unique Entitlement Key.
For the IBM Db2 Operators, you create a Docker Registry using the following command to add an Entitlement Key to a namespace:
oc create secret docker-registry ibm-registry \
--docker-username=cp \
--docker-password=myEntitlementKey \
--docker-server=cp.icr.io \
--namespace=myNamespace
Where ibm-registry
is the secret name, cp
is the username, and myEntitlementKey
is the password that stands for your unique Entitlement Key.
Note: You also use kubectl tool instead of oc tool to create the secret.
Alternative Procedure
You can also put the information in the OpenShift Container Platform global cluster pull secret to pull images for your Kubernetes installation.
To create a pull secret to pull images from the IBM Cloud® Entitled Registry, you use cp.icr.io
in the docker-server
field and cp
in the docker-username
field. In addition, you ensure to
use a valid email address (associated to your IBMId) in the docker-email
field and copy the Entitlement Key within the double quotation marks in the docker-password
field.