Proposed title of this feature request

Jaeger deprecation

What is the nature and description of the request?

After Tempo and OTel operator reaching GA, the Red Hat OpenShift distributed tracing platform will be focused on only supporting one backend for distributed tracing. Deprecation notices were created in TRACING-3199, and this task aims to be the realization of such notice.

Why does the customer need this? (List the business requirements)

In order to have one platform supported by Red Hat that is integrated with the whole Observability stack.

List any affected packages or components.

RHOSDT based on Jaeger

Docs

Other info

Jaeger-agent is going to be removed very soon https://github.com/jaegertracing/jaeger/issues/4739 This has implication on our product and code in the jaeger-operator. For instance the operator injects agent into query pod. The query used to be instrumented with jaeger-client (reporting data via jaeger UDP), now it is instrumented with OTEL and reports OTLP via gRPC.

We might need to do engineering work to maintain/deprecate the Jaeger agent separately, since potentially the agent might get deprecated upstream before we deprecate all Jaeger.