-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore: upgrade jaegertracing to v2.8.0 #2389
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Roman Dmytrenko <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @erka thx for that!
I know that the PR is still in draft but I wanted to take a look and left some comments.
Let me know when that is ready and I can take a closer look and test it out!
Co-authored-by: Juliano Costa <[email protected]>
Co-authored-by: Juliano Costa <[email protected]>
Co-authored-by: Juliano Costa <[email protected]>
Signed-off-by: Roman Dmytrenko <[email protected]>
@julianocosta89 While it works fine with docker compose, the Helm chart for Jaeger v2 hasn’t been officially released yet. I’m not sure what the best workaround is to use the jaegertracing/helm-charts@v2 branch with helm in this case. Do you have any advice? |
good question! @puckpuck any ideas? |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Changes
Upgrade Jaeger to v2.8.0
Merge Requirements
For new features contributions, please make sure you have completed the following
essential items:
CHANGELOG.md
updated to document new feature additions