Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

Chapter 7. Manually injecting sidecars

For controller types other than Deployments (for example, StatefulSets, DaemonSets, etc.), you can manually define the Jaeger Agent sidecar in your specification.

The following snippet shows the manual definition you can include in your containers section for a Jaeger Agent sidecar:

example sidecar definition for a StatefulSet

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: example-statefulset
  namespace: example-ns
  labels:
    app: example-app
spec:

    spec:
      containers:
        - name: example-app
          image: acme/myapp:myversion
          ports:
            - containerPort: 8080
              protocol: TCP
        - name: jaeger-agent
          image: registry.redhat.io/distributed-tracing/jaeger-agent-rhel7:<version>
           # The agent version must match the operator version
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 5775
              name: zk-compact-trft
              protocol: UDP
            - containerPort: 5778
              name: config-rest
              protocol: TCP
            - containerPort: 6831
              name: jg-compact-trft
              protocol: UDP
            - containerPort: 6832
              name: jg-binary-trft
              protocol: UDP
            - containerPort: 14271
              name: admin-http
              protocol: TCP
          args:
            - --reporter.grpc.host-port=dns:///jaeger-collector-headless.example-ns:14250
            - --reporter.type=grpc
Copy to Clipboard Toggle word wrap

The Jaeger Agent can then be accessed at its default location on localhost.

7.1. Upgrading Jaeger
Copia collegamento

The 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. The OLM queries for available Operators as well as upgrades for installed Operators. For more information about how OpenShift Container Platform handled upgrades, refer to the Operator Lifecycle Manager documentation.

The update approach used by the Jaeger Operator upgrades the managed Jaeger instances to the version associated with the Operator. Whenever a new version of the Jaeger Operator is installed, all the Jaeger application instances managed by the Operator will be upgraded to the Operator’s version. For example, if version 1.10 is installed (both Operator and backend components) and the Operator is upgraded to version 1.11, then as soon as the Operator upgrade has completed, the Operator will scan for running Jaeger instances and upgrade them to 1.11 as well.

7.2. Removing Jaeger
Copia collegamento

The steps for removing Jaeger from an OpenShift Container Platform cluster are as follows:

  1. Shut down any Jaeger pods.
  2. Remove any Jaeger instances.
  3. Remove the Jaeger Operator.

7.2.1. Removing a Jaeger instance using the web console
Copia collegamento

Note

When deleting an instance that uses the in-memory storage, all data will be permanently lost. Data stored in a persistent storage (such as Elasticsearch) will not be deleted when a Jaeger 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, jaeger-system.
  4. Click the Jaeger 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.

7.2.2. Removing a Jaeger instance from the CLI
Copia collegamento

  1. Log in to the OpenShift Container Platform CLI. 

    $ oc login
    Copy to Clipboard Toggle word wrap

  2. To display the Jaeger instances run the command: 

    $ oc get deployments -n <jaeger-project>
    Copy to Clipboard Toggle word wrap

    The names of operators have the suffix -operator. The following example shows two Jaeger Operators and four Jaeger instances: 

    $ oc get deployments -n jaeger-system
    Copy to Clipboard Toggle word wrap

    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
    Copy to Clipboard Toggle word wrap

  3. To remove an instance of Jaeger, run the command: 

    $ oc delete jaeger <deployment-name> -n <jaeger-project>
    Copy to Clipboard Toggle word wrap

    For example, 

    $ oc delete jaeger tracing2 -n jaeger-system
    Copy to Clipboard Toggle word wrap

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

    $ oc get deployments -n <jaeger-project>
    Copy to Clipboard Toggle word wrap

    For example, 

    $ oc get deployments -n jaeger-system
    Copy to Clipboard Toggle word wrap

    Should generate output similar to the following: 

    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
    Copy to Clipboard Toggle word wrap

7.2.3. Removing the Jaeger Operator
Copia collegamento

Procedure

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

    • Remove the Jaeger Operator.
    • After the Jaeger Operator has been removed, if appropriate, remove the Elasticsearch Operator.
Torna in cima
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2025 Red Hat