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
×

Removing distributed tracing

The steps for removing Red Hat OpenShift distributed tracing from an OpenShift Container Platform cluster are as follows:

  1. Shut down any Red Hat OpenShift distributed tracing pods.

  2. Remove any Red Hat OpenShift distributed tracing instances.

  3. Remove the Red Hat OpenShift distributed tracing platform Operator.

  4. Remove the Red Hat OpenShift distributed tracing data collection Operator.

Removing a Red Hat OpenShift distributed tracing platform instance using the web console

When deleting an instance that uses the in-memory storage, all data is permanently lost. Data stored in a persistent storage such as Elasticsearch is not be deleted when a Red Hat OpenShift distributed tracing platform instance is removed.
Procedure

  1. Log in to the OpenShift Container Platform web console.

  2. Navigate to Operators → Installed Operators.

  3. Select the name of the project where the Operators are installed from the Project menu, for example, openshift-operators.

  4. Click the Red Hat OpenShift distributed tracing platform Operator.

  5. Click the Jaeger tab.

  6. Click the Options menu kebab next to the instance you want to delete and select Delete Jaeger.

  7. In the confirmation message, click Delete.

Removing a Red Hat OpenShift distributed tracing platform instance from the CLI

  1. Log in to the OpenShift Container Platform CLI.

    $ oc login --username=<NAMEOFUSER>

  2. To display the distributed tracing platform instances run the command:

    $ oc get deployments -n <jaeger-project>

    For example,

    $ oc get deployments -n openshift-operators

    The names of Operators have the suffix -operator. The following example shows two Red Hat OpenShift distributed tracing platform Operators and four distributed tracing platform instances:

    $ oc get deployments -n openshift-operators

    You should see output similar to the following:

    NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
elasticsearch-operator   1/1     1            1           93m
jaeger-operator          1/1     1            1           49m
jaeger-test              1/1     1            1           7m23s
jaeger-test2             1/1     1            1           6m48s
tracing1                 1/1     1            1           7m8s
tracing2                 1/1     1            1           35m

  3. To remove an instance of distributed tracing platform, run the following command:

    $ oc delete jaeger <deployment-name> -n <jaeger-project>

    For example:

    $ oc delete jaeger tracing2 -n openshift-operators

  4. To verify the deletion, run the oc get deployments command again:

    $ oc get deployments -n <jaeger-project>

    For example:

    $ oc get deployments -n openshift-operators

    You should see generated output that is similar to the following example:

    NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
elasticsearch-operator   1/1     1            1           94m
jaeger-operator          1/1     1            1           50m
jaeger-test              1/1     1            1           8m14s
jaeger-test2             1/1     1            1           7m39s
tracing1                 1/1     1            1           7m59s

Removing the Red Hat OpenShift distributed tracing Operators

Procedure

  1. Follow the instructions for Deleting Operators from a cluster.

    • Remove the Red Hat OpenShift distributed tracing platform Operator.

  • After the Red Hat OpenShift distributed tracing platform Operator has been removed, if appropriate, remove the OpenShift Elasticsearch Operator.