Kibana pod is not created after deploying clusterlogging instance

Issue

• Kibana pod is not created after deployment of clusterlogging instance.

• Elasticsearch-operator pod is streaming below logs repetitively:

  2022-07-08T12:47:07.537108125Z {"_ts":"2022-07-08T12:47:07.536933174Z","_level":"0","_component":"elasticsearch-operator_controller_kibana-controller","_message":"Reconciler error","_error":{"cause":{"msg":"ImageStream tag contains no images","name":"oauth-proxy","namespace":"openshift","tag":"v4.4"},"msg":"Failed to get oauth-proxy image"},"name":"kibana","namespace":"openshift-logging"}
  2022-07-08T12:47:34.974370921Z {"_ts":"2022-07-08T12:47:34.974267572Z","_level":"0","_component":"elasticsearch-operator_controller_kibana-controller","_message":"Reconciler error","_error":{"cause":{"msg":"ImageStream tag contains no images","name":"oauth-proxy","namespace":"openshift","tag":"v4.4"},"msg":"Failed to get oauth-proxy image"},"name":"kibana","namespace":"openshift-logging"}
  

• oauth-proxy imagestream shows below status:

  lastTransitionTime: "2022-07-11T12:47:10Z"
  message: 'Internal error occurred [registry.ocp4.example.com:8443/ocp4/openshift4@sha256:d787f47ee2a410f924ea00b2428f0cf2275eb059adac96ca1b69c71ad20ccb1d: Get "https://registry.ocp4.example.com:8443/v2/": x509: certificate signed by unknown authority, quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:d787f47ee2a410f924ea00b2428f0cf2275eb059adac96ca1b69c71ad20ccb1d: Get "https://quay.io/v2/": dial tcp: lookup quay.io on 10.0.0.1:53: server misbehaving]'