Since [this discussion|https://coreos.slack.com/archives/C02939DP5L5/p1638454166398000?thread_ts=1638453120.396000&cid=C02939DP5L5] we are changing the scope of this task:

For now, we don't know how the logging team is going to secure their loki components pods.
When you deploy loki-operator, everything is available in the openshift-logging namespace and you just need to specify the X-Scope-OrgID header to access.

After we implement this, we can create a followup task to implement any other authenticatin mechanism, if it changes in the future or we need tu support more Loki configurations.

Old task description:

Since we use Loki operator, we need to manage authentication through a gateway to access loki components on OpenShift.

This authentication is already done on Grafana side using "Forward OAuth Identity" feature.

You need to implement the Console Plugin side to be able to query Loki either :

• Passing the current user authenticated
• Using a service account (configured in the CRD)