from https://bugzilla.redhat.com/show_bug.cgi?id=1925050

Description of problem:
Jaeger pod fails on Disconnected cluster with pull errors for registry.redhat.io/openshift4/ose-oauth-proxy:latest

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Successfully created jaeger operator
2. Jaeger pod fails

1. oc get pods -n istio-system
   NAME READY STATUS RESTARTS AGE
   grafana-d9794f557-7bxjv 2/2 Running 0 22h
   istio-egressgateway-7988d4487d-4bch4 1/1 Running 0 22h
   istio-ingressgateway-cfdfb66ff-rm8bb 1/1 Running 0 22h
   istiod-basic-7d8ccd96f7-vlbkq 1/1 Running 0 22h
   jaeger-7cbffc574c-nv9fh 1/2 ImagePullBackOff 0 22h
   kiali-597cdc4485-wttrz 1/1 Running 0 151m
   prometheus-59f47d96-9lqq2 3/3 Running 0 22h

1. oc logs pod/jaeger-7cbffc574c-nv9fh -n istio-system -c oauth-proxy
   Error from server (BadRequest): container "oauth-proxy" in pod "jaeger-7cbffc574c-nv9fh" is waiting to start: trying and failing to pull image

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulling 45m (x255 over 22h) kubelet Pulling image "registry.redhat.io/openshift4/ose-oauth-proxy:latest"
Warning Failed 21m (x5768 over 22h) kubelet Error: ImagePullBackOff
Normal BackOff 68s (x5855 over 22h) kubelet Back-off pulling image "registry.redhat.io/openshift4/ose-oauth-proxy:latest"
3.

Actual results:
Jaeger pod run fails for oauth-proxy container.

Expected results:
Jaeger pod should run successfully for oauth-proxy container.

Additional info: