-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review any security implications with OpenTelemetry Collector Jaeger receivers/exporters #2156
Comments
what is the goal of this ticket vs. #1718? |
This was moved from the jaeger-opentelemetry-collector repo, so was referring to security implications related to OpenTelemetry Collector receivers/exporters. |
The missing part is the TLS configuration in Jaeger gRPC exporter. I will submit a PR to OTEL. |
Replicated @jpkrohling deployment from jaegertracing/jaeger-opentelemetry-collector#22 with Jaeger OTEL components. It uses TLS between agent and collector. But we need also mTLS. Jager OTEL collector: receivers:
jaeger:
protocols:
grpc:
endpoint: "localhost:14250"
tls_credentials:
cert_file: /home/ploffay/projects/opentelemetry/opentelemetry-collector/receiver/jaegerreceiver/testdata/certificate.pem
key_file: /home/ploffay/projects/opentelemetry/opentelemetry-collector/receiver/jaegerreceiver/testdata/key.pem
service:
pipelines:
traces:
receivers: [jaeger] Jaeger OTEL agent: exporters:
jaeger:
endpoint: "localhost:14250"
cert_pem_file: /home/ploffay/projects/opentelemetry/opentelemetry-collector/receiver/jaegerreceiver/testdata/certificate.pem
server_name_override: opentelemetry.io
extensions:
health_check:
port: 13134 |
PR to add mTLS to gRPC exporters We need also TLS for remote sampling strategies open-telemetry/opentelemetry-collector#461 |
I am closing this as done. The last part is to expose configure TLS config via flags but that is a separate issue. |
Re: #1718
The text was updated successfully, but these errors were encountered: