You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like Eraser to add the ability to support TLS for the eraser client for otlp metrics.
The underlying client (otlphttpmetrics) already supports this, see here
It can either be done through exposing these environment variables:
OTEL_EXPORTER_OTLP_CERTIFICATE/OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE
OTEL_EXPORTER_OTLP_CLIENT_KEY/OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY
I do not mind doing this work myself (I already somewhat started), just need to know if there are any considerations that you have with regards to the work, or if I am missing some crucial key points that would invalidate this work.
Are you willing to submit PRs to contribute to this feature request?
Yes, I am willing to implement it.
The text was updated successfully, but these errors were encountered:
ideally, we should do https by default. we can integrate with https://github.com/open-policy-agent/cert-controller to auto generate the certificates and rotate continously. also have an option for user to specify their own certs instead of auto gen.
would you be interested in creating a design doc for this?
What kind of request is this?
Feature
What is your request or suggestion?
I would like Eraser to add the ability to support TLS for the eraser client for otlp metrics.
The underlying client (otlphttpmetrics) already supports this, see here
It can either be done through exposing these environment variables:
OTEL_EXPORTER_OTLP_CERTIFICATE/OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE
OTEL_EXPORTER_OTLP_CLIENT_KEY/OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY
Or alternatively set up using this
I do not mind doing this work myself (I already somewhat started), just need to know if there are any considerations that you have with regards to the work, or if I am missing some crucial key points that would invalidate this work.
Are you willing to submit PRs to contribute to this feature request?
The text was updated successfully, but these errors were encountered: