Till logging 5.3 customer was able to deploy elasticsearch operator in 'openshift-logging' namespace but after 5.4 if the customer deploys elasticsearch operator in the `openshift-logging` namespace then kibana pod is not starting.

Errors in elasticsearch Operator 5.4:

~~~
{"_ts":"2022-06-20T17:14:18.610236923Z","_level":"0","_component":"elasticsearch-operator_controller_kibana-controller","_message":"Reconciler error","_error":{"cause":{"cause":{"ErrStatus":{"metadata":{},"status":"Failure","message":"ImageStream.image.openshift.io \"oauth-proxy\" not found","reason":"NotFound","details":{"name":"oauth-proxy","group":"image.openshift.io","kind":"ImageStream"},"code":404}},"msg":"failed to get ImageStream","name":"oauth-proxy","namespace":"openshift"},"msg":"Failed to get oauth-proxy image"},"name":"kibana","namespace":"openshift-logging"}
~~~ 

Reason for the ask:

Reason for installing the ES operator in openshift-logging was to avoid users from installing their own logging stack in different namespaces.