This is a cache of https://docs.openshift.com/container-platform/4.6/distr_tracing/distr_tracing_install/distr-tracing-updating.html. It is a snapshot of the page at 2024-11-22T23:55:39.628+0000.
Upgrading distributed tracing - Distributed tracing installation | Distributed tracing | OpenShift Container Platform 4.6
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Upgrading distributed tracing

Operator Lifecycle Manager (OLM) controls the installation, upgrade, and role-based access control (RBAC) of Operators in a cluster. The OLM runs by default in OpenShift Container Platform. OLM queries for available Operators as well as upgrades for installed Operators. For more information about how OpenShift Container Platform handles upgrades, see the Operator Lifecycle Manager documentation.

During an update, the Red Hat OpenShift distributed tracing Operators upgrade the managed distributed tracing instances to the version associated with the Operator. Whenever a new version of the Red Hat OpenShift distributed tracing platform Operator is installed, all the distributed tracing platform application instances managed by the Operator are upgraded to the Operator’s version. For example, after upgrading the Operator from 1.10 installed to 1.11, the Operator scans for running distributed tracing platform instances and upgrades them to 1.11 as well.

For specific instructions on how to update the OpenShift Elasticsearch Operator, see Updating OpenShift Logging.

Changing the Operator channel for 2.0

Red Hat OpenShift distributed tracing 2.0.0 made the following changes:

  • Renamed the Red Hat OpenShift Jaeger Operator to the Red Hat OpenShift distributed tracing platform Operator.

  • Stopped support for individual release channels. Going forward, the Red Hat OpenShift distributed tracing platform Operator will only support the stable Operator channel. Maintenance channels, for example 1.24-stable, will no longer be supported by future Operators.

As part of the update to version 2.0, you must update your OpenShift Elasticsearch and Red Hat OpenShift distributed tracing platform Operator subscriptions.

Prerequisites

  • The OpenShift Container Platform version is 4.6 or later.

  • You have updated the OpenShift Elasticsearch Operator.

  • You have backed up the Jaeger custom resource file.

  • An account with the cluster-admin role. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin role.

If you have not already updated your OpenShift Elasticsearch Operator as described in Updating OpenShift Logging complete that update before updating your Red Hat OpenShift distributed tracing platform Operator.

For instructions on how to update the Operator channel, see Upgrading installed Operators.