Is it possible to set headers in the telemetry metrics sink?

[seanankenbruck]

I am running Envoy proxy in an environment where my opentelemetry collector requires the header X-Scope-OrgId to route metrics data to the appropriate tenant. In the documentation , it is not clear if you can set custom headers on the sink definition. For access logs and tracing, it seems like this is possible but for my purposes I would need to set the header on metrics as well.

From the Envoy Gatewy docs, the sample is shown below:

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: eg
  namespace: envoy-gateway-system
spec:
  gatewayClassName: eg
  infrastructure:
    parametersRef:
      group: gateway.envoyproxy.io
      kind: EnvoyProxy
      name: otel-sink
  listeners:
    - name: http
      protocol: HTTP
      port: 80
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: otel-sink
  namespace: envoy-gateway-system
spec:
  telemetry:
    metrics:
      sinks:
        - type: OpenTelemetry
          openTelemetry:
            host: otel-collector.monitoring.svc.cluster.local
            port: 4317

Is it possible to set a custom header in this sink definition?

[arkodg]

cc @zirain

[zirain]

it's not support today, but shouldn't be hard to extend.

[arkodg]

tracked with #5787