Obtaining and applying your IBM Entitled Registry entitlement key
The IBM® Entitled Registry contains software images for
the IBM App Connect components that can be used to create your
authoring and runtime environments, and other resources. To allow the IBM App Connect Operator to pull these software images from the IBM Entitled Registry, you must first obtain your entitlement key (if
you do not already have one) and then supply it as a Kubernetes pull secret. If you use the secret
name ibm-entitlement-key
, this secret is automatically used to pull images from the
IBM Entitled Registry.
You can add a pull secret to each namespace in which you want to create your authoring and runtime environments, and resources. Or, you can add a global pull secret, which enables deployment of the authoring and runtime environments, and resources in all namespaces. A cluster administrator or a user with the required permissions must complete this procedure.
If you installed the Operator in an air-gapped environment on Red Hat® OpenShift®, an entitlement was obtained and applied as part of the mirroring process. Therefore, you can skip this task.
If you installed the Operator in an online environment on Red Hat OpenShift or Kubernetes, you need to complete this task.
Obtaining an entitlement key
Procedure
To obtain an entitlement key, complete the following steps:
Adding an entitlement key to a namespace
You can use standard Kubernetes tools to create a pull secret (which contains your entitlement key) in the installation namespace of your IBM App Connect components. You must create the secret in every namespace where you want to install IBM App Connect components.
Procedure
To add an entitlement key to a namespace, complete the following step.
ibm-entitlement-key
as the secret name, cp
as the user name, your
entitlement key as the password, and your required target namespace: oc create secret docker-registry ibm-entitlement-key \
--docker-username=cp \
--docker-password=myEntitlementKey \
--docker-server=cp.icr.io \
--namespace=myNamespace
You can also use the kubectl tool instead of the oc tool to create the secret.
Adding a global pull secret for all namespaces
Procedure
To add a pull secret for the whole cluster, complete the following steps: