Using the version: registry.k8s.io/ingress-nginx/opentelemetry:v20230312-helm-chart-4.5.2-28-g66a760794@sha256:40f766ac4a9832f36f217bb0e98d44c8d38faeccbfe861fbc1a76af7e9ab257f when i set a auth location like:
The open telemetry headers are available only for the location / backend but not for the location /auth backend.
What is the expected behavior?
I want to have the same trace id in both backends: (application and authorizer)
What is the actual behavior?
I have only the trace id generated for the application, but the open telemetry headers are not sent to the authorizer app.
Describe your environment EKS 1.24 Nginx:
Using the version:
registry.k8s.io/ingress-nginx/opentelemetry:v20230312-helm-chart-4.5.2-28-g66a760794@sha256:40f766ac4a9832f36f217bb0e98d44c8d38faeccbfe861fbc1a76af7e9ab257f
when i set a auth location like:The open telemetry headers are available only for the
location /
backend but not for thelocation /auth
backend.What is the expected behavior? I want to have the same trace id in both backends: (application and authorizer)
What is the actual behavior? I have only the trace id generated for the application, but the open telemetry headers are not sent to the authorizer app.