Currently running: v1.56.0
The only breaking change I could find in the release notes was this one remark on a PR:
We do configure a TLS cert on the query service. But I don't think we have to worry because we aren't doing anything fancy with cert reloads?
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T340551 distributed tracing epic | |||
| Open | None | T320549 distributed tracing v0 [minimum viable] | |||
| Resolved | CDanis | T375123 Archiving a trace more than once will duplicate all spans | |||
| Resolved | • herron | T376904 Upgrade to Jaeger v1.62.0 | |||
| Open | None | T377756 jaeger-query: setup method for testing new/test versions |
Change #1080727 had a related patch set uploaded (by Herron; author: Herron):
[operations/docker-images/production-images@master] jaeger: upgrade images to 1.62
Change #1080727 merged by Herron:
[operations/docker-images/production-images@master] jaeger: upgrade images to 1.62
Change #1081181 had a related patch set uploaded (by Herron; author: Herron):
[operations/deployment-charts@master] jaeger: bump to 1.62-1
Change #1081181 merged by jenkins-bot:
[operations/deployment-charts@master] jaeger: bump to 1.62-1
Change #1082006 had a related patch set uploaded (by Herron; author: Herron):
[operations/docker-images/production-images@master] jaeger: bump jaeger-builder version to 1.62.0
Change #1082006 merged by Herron:
[operations/docker-images/production-images@master] jaeger: bump jaeger-builder version to 1.62.0
https://trace.wikimedia.org is now running 1.62.0.
Didn't get to the trace-next part yet so created T377756 to keep tabs on that idea