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
Once Jaeger-v2 (jaegertracing/jaeger#4843) reaches production readiness and feature parity, we should support it in the operator.
Problem
Jaeger-v2 is based on OpenTelemetry Collector and uses completely different configuration mechanism:
all configuration is done via config files, not CLI flags or env vars (although some env vars are supported by telemetry SDKs)
it is a single binary that can be deployed into different roles (collector, query, etc.) also based on configuration, but in this case with structural config changes, not just tweaking parameters
Proposal
I would like to hear what maintainers of this repo think about the best approach. Can we come up with a roadmap of how jaeger-v2 will be supported by the operator? Is there some common approach we can use with the OTEL operator?
Open questions
Is it worth maintaining both helm charts and operator?
The text was updated successfully, but these errors were encountered:
Requirement
Once Jaeger-v2 (jaegertracing/jaeger#4843) reaches production readiness and feature parity, we should support it in the operator.
Problem
Jaeger-v2 is based on OpenTelemetry Collector and uses completely different configuration mechanism:
Proposal
I would like to hear what maintainers of this repo think about the best approach. Can we come up with a roadmap of how jaeger-v2 will be supported by the operator? Is there some common approach we can use with the OTEL operator?
Open questions
The text was updated successfully, but these errors were encountered: