-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
1
-
False
-
None
-
False
-
Tracing Sprint # 241, Tracing Sprint # 242, Tracing Sprint # 243
During TRACING-1606 we implemented an E2E test to ensure the outside cluster feature works properly in Kubernetes for the Jaeger Operator. This feature consists on exposing the collector outside the cluster and ensure the traffic is reached.
During TRACING-1339 it was documented (but not published) how to expose the collector for Jaeger. In OSSMDOC-145, the solution was changed to use OpenTelemetry. Since for the multicluster (TRACING-2287) OpenTelemetry will be used, it makes sense to test the feature in OpenTelemetry.
The solutions proposed in TRACING-1339 and some upstream issues, seem to not work or being really tricky. So, it makes more sense to do it using OpenTelemetry.
We need to add a test to ensure this scenario works properly.
- is related to
-
TRACING-2632 Support multi-cluster in RHOSDT
- Closed
- is triggering
-
TRACING-3218 OTEL Collector OpenShift Route is not properly exposed via CRD
- Closed
- relates to
-
TRACING-2552 MultiCluster: QE plan
- Closed