Hi,
Im setting our future production environment, so im using advanced image and setup license service.
ibm-entitlement-key is in same namespace than operator and IBM MQ Native HA instance. I have and old version of MQ running with other version of the Operator and i didnt get that issue.
------------------------------
Andres Colodrero
------------------------------
Original Message:
Sent: Thu August 15, 2024 03:51 AM
From: Martin Evans
Subject: MQ Operator: Unable to retrieve some image pull secrets (sa-mq-operator);
Hi Andres,
This looks like an OpenShift/k8s security feature, the service account running IBM MQ needs to have access to the secret but other accounts/namespace should not have access. I think it is possible to grant access to secrets in different namespaces but I don't think it is straightforward, I always put the image pull secret in the namespace where I am deploying IBM MQ. Note that you do not need an image pull secret for the IBM MQ Operator and the Developer container images.
------------------------------
Regards,
Martin Evans
IBM MQ Technical Product Manager
Original Message:
Sent: Wed August 14, 2024 11:24 AM
From: Andres Colodrero
Subject: MQ Operator: Unable to retrieve some image pull secrets (sa-mq-operator);
HI,
Deploying a MQ QueueManager with Latest Operator version (3.2.3) fails with this message:
Unable to retrieve some image pull secrets (sa-mq-operator);
where "mq-operator" is the namespace.
I have previously create the secret ibm-entitlement-key, but got this error.
This was fixed after i copied the ibm-entitlement-key to "sa-mq-operator"
I didnt see any related docs in the documentations.
------------------------------
Andres Colodrero
------------------------------