When deploying Service Mesh on SNO in a disconnected environment , the Jaeger Pod frequently goes into Pending state

$ oc describe pod -n istio-system jaeger-6785d9fd7b-xxxxx
<...>
  Normal   Pulling         6m42s (x3 over 7m25s)   kubelet            Pulling image "registry.redhat.io/openshift4/ose-oauth-proxy:latest"
  Warning  Failed          6m42s (x3 over 7m25s)   kubelet            Failed to pull image "registry.redhat.io/openshift4/ose-oauth-proxy:latest": rpc error: code = Unknown desc = pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp: lookup registry.redhat.io on 172.110.12.31:53: server misbehaving
  Warning  Failed          6m42s (x3 over 7m25s)   kubelet            Error: ErrImagePull
  Warning  Failed          6m28s (x6 over 7m25s)   kubelet            Error: ImagePullBackOff
  Normal   BackOff         2m24s (x23 over 7m25s)  kubelet            Back-off pulling image "registry.redhat.io/openshift4/ose-oauth-proxy:latest"

$ oc get deployment jaeger -n istio-system -o yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jaeger
  namespace: istio-system
spec:
  template:
    metadata:
    spec:
      containers:
      - args:
        image: registry.redhat.io/openshift4/ose-oauth-proxy:latest    #<------

$ oc get is -n openshift oauth-proxy -o yaml
apiVersion: image.openshift.io/v1
kind: ImageStream
metadata:
  name: oauth-proxy
  namespace: openshift
spec:
  lookupPolicy:
    local: false
  tags:
  - annotations: null
    from:
      kind: DockerImage
      name: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9c0cf8f4d56f16d74534c21a67cab0bbc524da3ef38a84116c4080bdc00e46ca    #<------
    generation: 5
    importPolicy:
      scheduled: true
    name: v4.4
    referencePolicy:
      type: Source

$ oc -n openshift-operators logs jaeger-operator-57cc46697c-xxxxx -c jaeger-operator | head -n 5 
2023-05-25T05:21:11.102501612Z 1.6849920711024122e+09	INFO	Versions	{"os": "linux", "arch": "amd64", "version": "go1.19.2", "jaeger-operator": "v1.39.0", "identity": "openshift-operators.jaeger-operator", "jaeger": "1.39.0"}
2023-05-25T05:21:11.102712914Z 1.6849920711027002e+09	INFO	setup	watching namespace(s)	{"namespaces": ""}
2023-05-25T05:21:12.153493367Z I0525 05:21:12.153354       1 request.go:682] Waited for 1.035593138s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/authorization.openshift.io/v1?timeout=32s
2023-05-25T05:21:18.906113267Z 1.684992078906025e+09	INFO	controller-runtime.metrics	Metrics server is starting to listen	{"addr": "0.0.0.0:8383"}
2023-05-25T05:21:18.909317196Z 1.6849920789092264e+09	ERROR	failed to determine the platform capabilities, auto-detected properties will remain the same until next cycle.	{"error": "<nil>; Error getting resources for server group route.openshift.io: the server is currently unable to handle the request"} #<------
<...>
2023-05-25T05:21:19.007446090Z 1.6849920790074377e+09	INFO	Not running on OpenShift, so won't configure OAuthProxy imagestream.

$ oc get -n openshift-apiserver pods apiserver-7fc4749f56-xxxxx -o yaml
apiVersion: v1
kind: Pod
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2023-05-25T05:21:09Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2023-05-25T05:21:19Z"   #<------ It is overlap the initialization of Jaeger Operator pod
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2023-05-25T05:21:19Z"
    status: "True"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2023-05-25T05:20:58Z"
    status: "True"
    type: PodScheduled
  startTime: "2023-05-25T05:20:58Z"