In 2.5, we:

• Added support for Tempo and OTEL with OSSM
• Formally deprecated Jaeger and Elasticsearch as operators.

Jaeger and Elasticsearch will be EOLed by the tracing team around the same time that 2.6 is EOLed, thus, we must ask our customers to move off of Jaeger/ES in the 2.6 timeframe and ensure that new OSSM users do not start with Jaeger/ES. OTEL + Tempo is now the canonical tracing setup that Red Hat supports.

Thus, in 2.6, we need to:

• Disable the OSSM operator's Jaeger and ES installation by default. New installations should now have no tracing is enabled via the OSSM operator. Users should NOT be directed to install the Jaeger or Elasticsearch operators - this documentation should be removed or move to a separate section where it is clearly marked as deprecated.
• Direct users to configure tracing with OTEL + Tempo. We will need to add additional documentation for OTEL, as this was not completed for 2.5. OTEL + Tempo in 2.5. This includes Kiali integration. This content should be similar if not identical for OSSM 3.0, so let's try to reuse.
• Address any issues raised against OTEL + Tempo in 2.5 Z streams (not an item for this epic, just noting).
• Provide a section on migrating from Jaeger to OTEL + Tempo, leveraging any content the tracing team has on this topic. We do not need to provide any content/guarantees beyond what the tracing team provides here. 
• Document in 2.6 release notes that this will be the final release of OSSM that includes support for Jaeger and ES - it will be removed in the next release. Customers should migrate to OTEL + Tempo.