That would be great, as in my case we're using Thanos, and query parameter is a hard requirement for us (like the namespace), and can't alter this requirement, as I don't have access to that component. For the Bearer token I use the ---prometheus.token-file cli flag, which is basically a secret token generated by an appopriate SA (for all-in-one), and I'm mounting it using:

extraSecretMounts:
    - name: prometheus-token
      mountPath: /tls
      secretName: jaeger-all-in-one-token
      readOnly: true

this, plus RoleBinding of ClusterRole type:

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: jaeger
  namespace: default
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: <ClusterRoleName>
subjects:
- kind: ServiceAccount
  name: jaeger-all-in-one
  namespace: default

but I'm getting an error which I can't make anything out of it, so I'm assuming is because of the missing required namespace parameter..., but not 100% sure...

msg":"HTTP handler, Internal Server Error","error":"failed executing metrics query: bad_response: readObjectStart: expect { or n, but found B, error found in #1 byte of ...|Bad Request|..., bigger context ...|Bad Request. The request or configuration is malfor|..."

cc @rbaumgar

@hkailantzis I don't know what is required in your environment.
In OpenShift you have two ports available

• 9091, requires a cluster role. access to all namespace data
• 9092, requires a namespace parameter where the token has access to
  https://www.redhat.com/en/blog/thanos-querier-versus-thanos-querier

@rbaumgar, is the 9092 case actually, where a namespace parameter is required...which is not supported by jaeger SPM as the moment right ?

@hkailantzis correct! I don't want to use a cluster role for SPM...

@yurishkuro, I want to try it out

If I understand the issue correctly, we want to send extra paramters to the promethes endpoint, right? I checked the documentation but couldn't find any such server-side handling for such extra parameters. Are you trying to use a proxy in between?

Moreover, the current implementation uses prometheus client library instead of directly calling the http route, which only allows the paramters time and timeout as extra optional parameters mentioned in the doc:
https://prometheus.io/docs/prometheus/latest/querying/api/

@akstron we pass api.Client to the api.v1 which is used for executing the actual HTTP requests. The client is a very small API that is easy to wrap in a decorator if we want to add some extra parameters to the URL.

I see, that makes sense. I will start working on it. Thanks!

@akstron we should only do this in Jaeger v2 (i.e. don't both with v1 CLI flags for these headers).