Description of problem:
-----------------------
Jaeger operator uses tag instead of the digest for openshift4/ose-oauth-proxy:4.2

It tries to pull "registry.redhat.io/openshift4/ose-oauth-proxy:latest" and "registry.redhat.io/openshift4/ose-oauth-proxy:4.2".

The customer is trying to install RHSM on OCP 4.5.7 on a disconnected cluster, they created a local Operator Lifecycle Manager and an ImageContentSourcePolicy. All the images mirrored locally are referenced by DIGEST in the ImageContentSourcePolicy. The customer installed the Operators but when they create the instance they get a fail from Jaeger. It tries to pull "registry.redhat.io/openshift4/ose-oauth-proxy:latest" and "registry.redhat.io/openshift4/ose-oauth-proxy:4.2". All images are mirrored and referred by digest but these 2.

I the deployment there is an image "ose-oauth-proxy" that is referred by TAG and not DIGEST in 2 places.
If there is an image referenced by TAG, OCP will not be able to pull it from the local image repo.

We are also looking for a possible workaround.

Version-Release number of selected component:
---------------------------------------------

• OCP v4.5.7

Actual results:
---------------

• It is not possible to deploy Red Hat OpenShift Jaeger in a disconnected cluster.

Expected results:
-----------------

• Deployment of Red Hat OpenShift Jaeger is successful.