Descheduler - Missing OTLP Headers

[HujinoKun]

Hello,

In the documentation, I didn't see anything about adding a header to send OLTP tracings.

How can I add it? Like this :

  tracing:
    collectorEndpoint: grafana-alloy.grafana-alloy.svc.cluster.local:4317
    transportCert: ""
    serviceName: "descheduler"
    serviceNamespace: "kube-system"
    sampleRate: 1.0
    fallbackToNoOpProviderOnError: true
    headers: "X-Scope-OrgID=alloy-tracing-metrics"

[ricardomaraschini]

I looked into it and this is indeed not supported. Is this a well established practice ? How often do people need to add custom headers ?

[HujinoKun]

I looked into it and this is indeed not supported. Is this a well established practice ? How often do people need to add custom headers ?

Hello,

In my case, I use grafana alloy and tempo suite, which must use the correct header to send the tracing.

And I manage my distribution according to the cluster and the application, and then play with overrides, for example.

[ingvagabund]

@HujinoKun I have no experience with the headers. Is this something that could be easily implemented? A good first issue for new contributors?

[HujinoKun]

@HujinoKun I have no experience with the headers. Is this something that could be easily implemented? A good first issue for new contributors?

Hello,

I can't comment on the simplicity of integration for managing the OTEL header, as I'm not a developer and am unfamiliar with Golang programming.

There is training and skill development required beforehand :/