🌆 Jaeger v1 End-of-life #6321
Labels
Comments
yurishkuro
added a commit
that referenced
this issue
Dec 7, 2024
## Which problem is this PR solving? - Part of #6321 ## Description of the changes - Print EOL notice from core v1 binaries ## How was this change tested? ``` $ go run ./cmd/all-in-one 2024/12/07 13:02:54 maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined ******************************************************************************* 🛑 WARNING: End-of-life Notice for Jaeger v1 You are currently running a v1 version of Jaeger, which is deprecated and will reach end-of-life on December 31st, 2025. This means there will be no further development, bug fixes, or security patches for v1 after this date. We strongly recommend migrating to Jaeger v2 for continued support and access to new features. For detailed migration instructions, please refer to the official Jaeger documentation: https://www.jaegertracing.io/docs/latest/migration/ Tracking issue: #6321 🛑 WARNING: End-of-life Notice for Jaeger v1 ******************************************************************************* 2024/12/07 13:02:54 application version: git-commit=, git-version=, build-date= {"level":"info","ts":1733594574.315758,"caller":"flags/service.go:123","msg":"Mounting metrics handler on admin server","route":"/metrics"} ``` --------- Signed-off-by: Yuri Shkuro <[email protected]>
|
Are there going to be all-in-one releases? |
|
Jaeger v2 binary is itself all-in-one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since we have officially released v2, it is time to set the timeline for end-of-life for Jaeger v1.
Timeline:
During the course of 2025 we will continue accepting bug fixes to v1 components, as well as potentially make improvements since they share a lot of the code with v2.
From Jan 01 2026 there will be no new releases of Jaeger v1 binaries.
The text was updated successfully, but these errors were encountered: