-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Deprecate Jaeger and Opentracing in favor of OpenTelemetry #8687
Comments
https://www.jaegertracing.io/docs/1.35/client-libraries/ <- Reference on the Jaeger clients being deprecated |
Probably we also need to know how many people are currently using this feature. |
Jaeger cli is deprecated so we can move this. |
jaeger-client-cpp is no longer fixing bugs jaegertracing/jaeger-client-cpp#292, so OpenTelemetry support has become more important |
What is blocking this, exactly? |
No blocker per se, but there is stabilization work in progress so lack of developer time. As soon as the higher priority stabiilization work is under control, some developer time will go into opentelemetry. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/assign |
We should keep an eye also on #10082 |
I think for #10082 we have reached an agreement. #10082 (comment) And I saw there has a PR #10151 works and relegated with this one. |
/assign |
We have to support opentracing for controller v1.9 builds so this PR #10913 needs to be cleaned up and merged after releasing controller v1.11 |
Controller v1.11 released so closing this issue /close |
@longwuyuan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
OTEL is around for a while. We even have a starting implementation in NGINX.
In an effort to simplify our code, the compilation times, etc we need to remove the features Jaeger and Opentracing and keep only opentelemetry.
To not break users, maybe we need to analyze when an old jaeger directive was used and configure otel to send proper traces. We need to check;
This is just a boilerplate issue, but we need to evolve it
/triage accepted
/kind cleanup
/priority important-longterm
The text was updated successfully, but these errors were encountered: