Details
-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
None
-
False
Description
Acceptance Criteria:
- Test that Users can reference a Distributed tracing instance in their installation config (by namespacedName ie <namespace>/<name>)
- the operator will update MeshConfig so that proxy traces are sent to that Tracing instance
- Document the procedure to setup and confirm traces.
Note: This should use the Tech Preview of Distributed Tracing 3, which is based on Grafana Temp (No longer Jaeger/ES), described here: https://docs.openshift.com/container-platform/4.9/distr_tracing/distributed-tracing-release-notes.html#distr-tracing-rn-technology-preview_distributed-tracing-release-notes
Tradeoff: Configuring tracing does not need to be automatic or simple as it was in Service Mesh 2 - it is ok if users have to set multiple values and define multiple CRDs. Consider also that users may want to connect to 3rd party tracing solutions using Zipkin instead. The aim h