Currently running: v1.56.0
The only breaking change I could find in the [[ https://github.com/jaegertracing/jaeger/releases | release notes ]] was this one remark on a PR:
* https://github.com/jaegertracing/jaeger/pull/6023#issuecomment-2380724591
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?
- [ ] Update jaeger's [[ https://wikitech.wikimedia.org/wiki/Kubernetes/Images#Production_images | production-images ]] subtree with the new version, build Docker images
- [ ] Helm values patch + deploy new version
- [ ] Would be nice to have a way to run a new/test version jaeger-query, but not required
- [ ] trace-next.wikimedia.org ?
- [ ] Deployment of just the query component; same k8s namespace should be fine