-
Notifications
You must be signed in to change notification settings - Fork 95
on operator install in openshift I get InvalidImageName #63
Comments
I over-rode the values in the CSR to fix this issue to come back with |
The value we provide in the CR seems to be ignored and is replaced by this, which comes from here. I tried patching the deployment with oc patch deployment deployment/prisma-cloud-compute-console-helm-operator -p '{"spec":{"template":{"spec":{"containers":[{"env":[{"name":"RELATED_IMAGE_CONSOLE","value":"registry-auth.twistlock.com/tw_xxxxxxxxxxxxx/twistlock/console:console_20_04_169"}],"name":"prisma-cloud-compute-console-helm-operator"}]}}}}' but I am assuming that this is undone by the Helm template. I've no idea how to use this operator right now. EDIT: I was able to update the image reference with |
Small folow up to say that I got the patch to work with the below command: oc patch "clusterserviceversion/prisma-cloud-compute-console-operator.v1.0.0" \
-n my-namespace \
-p '{"spec":{"install":{"spec":{"deployments":[{"name":"prisma-cloud-compute-console-helm-operator","spec":{"selector":{"matchLabels":{"name":"prisma-cloud-compute-console-helm-operator"}},"template":{"spec":{"containers":[{"name":"prisma-cloud-compute-console-helm-operator","env":[{"name":"RELATED_IMAGE_CONSOLE","value":"registry-auth.twistlock.com/tw_xxxxxxxx/twistlock/console:console_20_04_169"}]}]}}}}]}}}}' \
--type=merge \
--dry-run=server |
consoleImageName: registry-auth.twistlock.com/tw_<REPLACE_TWISTLOCK_TOKEN>/twistlock/console:console_20_04_163
but I changed the values in the CR that should have been replaced.
88s Warning OverrideValuesInUse twistlockconsole/twistlockconsole Chart value "consoleImageName" overridden to "registry-auth.twistlock.com/tw_<REPLACE_TWISTLOCK_TOKEN>/twistlock/console:console_20_04_169" by operator's watches.yaml
68s Warning OverrideValuesInUse twistlockconsole/twistlockconsole Chart value "consoleImageName" overridden to "registry-auth.twistlock.com/tw_<REPLACE_TWISTLOCK_TOKEN>/twistlock/console:console_20_04_169" by operator's watches.yaml
The text was updated successfully, but these errors were encountered: