Description of problem:
When installed, the AMQ Streams operator deploys with this containerImage:
categories: Streaming & Messaging
Red Hat AMQ Streams is a massively scalable, distributed, and high
performance data streaming platform based on Apache Kafka®.
Events show an image pull error because the image doesn't exist, and 404s:
Warning Failed 75m (x4 over 77m) kubelet, ip-172-29-225-159.us-west-2.compute.internal Failed
to pull image "registry.redhat.io/amq7/amq-streams-rhel7-
operator@sha256:4079eadd9a806adfbf3222f071c0498b17a6c54f9b8d199cf5af4961bcbdd83a": rpc error: code =
Unknown desc = Error reading manifest
sha256:4079eadd9a806adfbf3222f071c0498b17a6c54f9b8d199cf5af4961bcbdd83a in registry.redhat.io/amq7/amq-
streams-rhel7-operator: error parsing HTTP 404 response body: invalid character 'F' looking for
beginning of value: "File not found.\""
It appears that the new operator was rolled out before the containerImage was published to registry.redhat.io.
Version-Release number of selected component (if applicable):
AMQ Streams Operator v1.4.0
Steps to Reproduce:
1. Install AMQ Streams Operator via OperatorHub or OLM
2. Pull the yaml manifest and observe the containerImage
404 not found
URL matches image
We don't have a workaround at this time, because we aren't sure what CRD/Operator/configuration to change and where to point the operator at the correct image.