Hi, a customer entitled for ODM 8.11 is trying to deploy in certified Kubernetes. They refused to trade-up the ODM license by equivalent CP4BA entitlement.

When trying to deploy the helm chart release they got an HTTP 403 (forbidden) while pulling ODM images from cp.icr.io/cp/cp4a/odm.

My understading is that, like ODM entitled customer, they are allowed to deploy the chart. ¿isn't it? ¿Is this because ODM images are stored in the official CP4BA registry?

In such case I guess they can still upload ODM images to their local registry, but is not the preferred option.

Thanks.

------------------------------
Eduardo Izquierdo Lázaro
Automation Architect
DECIDE
Madrid
609893677
------------------------------

Hello Eduardo,

We think there is an issue with your image pull secret.

We documented its creation on https://github.com/DecisionsDev/odm-docker-kubernetes/tree/master/platform/azure#prepare-your-environment-for-the-odm-installation and its use later.

First, log in to MyIBM Container Software Library with the IBMid and password that are associated with the entitled software.

Then create the pull secret containing the ICR credentials:

kubectl create secret docker-registry registrysecret --docker-server=cp.icr.io \
                                                         --docker-username=cp \
                                                         --docker-password="<entitlementkey>" \
                                                         --docker-email=<email>

Finally you can start you Helm installation with the mandatory argument:

helm install <release> ibmcharts/ibm-odm-prod \
        --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=registrysecret

Plus your other parameters. Then it should work as expected.

Regards,

------------------------------
Pierre-Yves Lochou
------------------------------