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
Since we have officially released v2, it is time to set the timeline for end-of-life for Jaeger v1.
Timeline:
Jaeger 2.0 release in November 2024
Jaeger 1.x end-of-life is going to be Dec 31 2025
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.
The text was updated successfully, but these errors were encountered:
## 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]>
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.
The text was updated successfully, but these errors were encountered: