Support TLS for reporting internal spans from Jaeger query to collector

[kvaidas]

Requirement - what kind of business use case are you trying to solve?

TLS configuration options in jaeger-query - for reporting its own spans to the collector

Problem - what in Jaeger blocks you from solving the requirement?

TLS configuration options like tls.server-name or tls.skip-host-verify are not available in jaeger-query

Proposal - what do you suggest to solve the problem or improve the existing situation?

I believe the libraries used in jaeger might already have this functionality but it needs to be exposed through cli parameters and/or envvars

[pavolloffay]

Jaeger query uses https://github.com/jaegertracing/jaeger-client-go to report spans to the collector. The go client is configurable via env vars (see https://www.jaegertracing.io/docs/1.18/client-features/). At the moment there is no TLS support in the client libraries.

[kvaidas]

As I understand #2337 should create some groundwork for this to be implemented.

[pavolloffay]

no #2337 introduces TLS to query endpoints.