Connect TempoQuery Backend (Jaeger) to Kiali
With the latest changes to the tempo package, TempoQuery is exposed on tracing.bigbang.dev
and at port 16686
of tempo-tempo.tempo.svc
, this UI/backend is a Jaeger installation so we will need to up the resources for the tempoQuery pod (kiali requests use a lot of network and resources) in the package, and make sure the tracing inCluster backend for Kiali is pointing to "http://tempo-tempo.tempo.svc.cluster.local:16686"
instead of a jaeger service
AC:
-
Increased tempoQuery resources in Tempo package (with slightly smaller ones set in tests/test-values.yaml
-
Add logic in BigBang kiali Passthrough values to conditionally move the tracing backend URL to point to tempo over jaeger