Jaeger Deprecation and Removal in OpenShift

Solution Verified - Updated

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Distributed Tracing Platform (Jaeger)

Issue

  • When installing the Red Hat OpenShift Distributed Tracing Platform or OpenShift Service Mesh, there is a warning on OpenShift web console regarding the deprecation of Jaeger.

Resolution

Starting with the Red Hat Openshift distributed tracing platform 3.0, Jaeger and OpenShift Elasticsearch Operator are deprecated and will be removed in a future release. Red Hat will provide bug fixes and support for these features during the current release lifecycle, but these features will no longer receive enhancements and will be removed.

As an alternative to Red Hat OpenShift Distributed Tracing Platform (Jaeger), it is recommended to use Red Hat OpenShift Distributed Tracing Platform (Tempo) instead, together wit the Red Hat build of OpenTelemetry.

Notes about Tempo storage

  • Tempo requires object storage to store tracing data, and supports all major cloud object storage types. Refer to the object storage setup documentation for additional information.
  • Tempo also provides a TempoMonolithic instance which can serve as a great replacement for "Jaeger all-in-one", providing the ability to store traces in-memory or disk (not intended for production environments). More information can be found in this This content is not included.Blog post.

Jaeger usage with Service Mesh

The Distributed Tracing is an optional component of OpenShift Service Mesh. Refer to understanding distributed tracing in the Service Mesh documentation for additional information. Note that since the Jaeger and Elasticsearch operators are supported as part of OpenShift Distributed Tracing, they may reach end of life before OpenShift Service Mesh 3.0, and is no longer the default since version 2.6 as explained in Red Hat OpenShift Distributed Tracing Platform (Jaeger) default setting change . It will be required to migrate off of Jaeger and Elasticsearch before upgrading to OpenShift Service Mesh 3.0.

Root Cause

The Jaeger operator, supported by Red Hat OpenShift was deprecated in December 2023 with the release of the Red Hat Openshift distributed tracing platform 3.0 and This content is not included.General Availability of the Red Hat build of OpenTelemetry. It is expected that Jaeger Operator is be removed from the OpenShift Operator Catalog in November 2025.

The Observability team will continue providing support for critical CVEs, but users are highly encouraged to change to the new Tempo and OpenTelemetry stack as soon as possible.

Refer to OpenShift Operator Life Cycles for additional information.

Diagnostic Steps

Red Hat OpenShift distributed tracing platform based on Jaeger is installed.

SBR
Product(s)
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.