Requirement:
The query (UI) component needs to be secured. Permissionmanagement is required.

Problem:
Jaeger-Operator does not provide a solution to inject a sidecar for the query component over the jaeger crd.

Proposal:
Implement some sort of additional configuration options for the jaeger crd to be able to inject a sidecar to the query component.

An idea is to expand the jaeger crd like this:

apiVersion: v1
kind: Jaeger
  metadata:
    name: jaeger
    namespace: default
  spec:
    query:
      oauthProxy:
        enabled: true
        args: {}
        image: quay.io/keycloak/keycloak-gatekeeper:10.0.0
      options: {}
      resources: {}

Issue #113 is about the same topic.
An idea in the values.yaml of the Jaeger-Operator helm chart is:

jaeger:
  create: true
  spec:
    strategy: production
    query:
      oauthProxy:
        enabled: true
        image: quay.io/keycloak/keycloak-gatekeeper:10.0.0
        args:

A valid solution is already coded in a fork and a pull request will follow soon.