Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 2. Updating OpenShift Logging

You can update Logging for Red Hat OpenShift by modifying the Operator subscription update channel.

2.1. Understanding OpenShift Logging update considerations
Link kopieren

The following information describes the key considerations, constraints, and supported update paths for Logging for Red Hat OpenShift.

Logging for Red Hat OpenShift update considerations:

  • If you are on an Extended Update Support (EUS) release of Logging for Red Hat OpenShift, it is recommended to update to an EUS release.
  • You must update the Red Hat OpenShift Logging Operator and the Loki Operator to the same major and minor version.
  • The maximum supported update channel for Loki Operator is the N+2 version, where N is your current version. Updating to a version that is more than two versions newer is not supported.

You only need to update the Operators for Logging for Red Hat OpenShift that you have installed. The following list describes the high-level steps for updating Logging for Red Hat OpenShift.

Only the Red Hat OpenShift Logging Operator is installed
  1. Check the update readiness for the Red Hat OpenShift Logging Operator.
  2. Update the Red Hat OpenShift Logging Operator.
The Red Hat OpenShift Logging Operator and the Loki Operator are installed

Update the Operators in the following order:

Important

You must update the Red Hat OpenShift Logging Operator and the Loki Operator to the same channel.

  1. Check the update readiness for both the Loki Operator and the Red Hat OpenShift Logging Operator.
  2. Update the Loki Operator.
  3. Update the Red Hat OpenShift Logging Operator.
The Red Hat OpenShift Logging Operator, the Loki Operator, and Cluster Observability Operator (COO) are installed

Update the Operators in the following order:

Important

You must update the Red Hat OpenShift Logging Operator and the Loki Operator to the same channel.

  1. Check the update readiness for both the Loki Operator and the Red Hat OpenShift Logging Operator.
  2. Update the Loki Operator.
  3. Update the Red Hat OpenShift Logging Operator.
  4. Update the Cluster Observability Operator (COO).

2.2. Checking update readiness
Link kopieren

Check the readiness of installed Operators before updating Logging for Red Hat OpenShift. You can verify the status of the Red Hat OpenShift Logging Operator and the Loki Operator to ensure a safe update.

2.2.1. Checking update readiness of Red Hat OpenShift Logging Operator
Link kopieren

Before you update Red Hat OpenShift Logging Operator, ensure that there are no alerts listed and all pods run correctly. This check ensures a smooth update.

Prerequisites

  • You have installed Red Hat OpenShift Logging Operator v6.
  • You have administrator permissions.
  • You have access to the OpenShift Container Platform web console.
  • You have installed the OpenShift CLI (oc).

Procedure

  1. Verify that no alerts are listed for Red Hat OpenShift Logging Operator:

    1. Navigate to Observe > Alerting.

    2. Use this filter to check alerts: 

      Source: platform
Alert State: Firing
Label: namespace=openshift-logging

      Ensure that no upgrade-blocking alerts are listed.

  2. In the OpenShift CLI (oc), verify that all the pods have all the containers in the READY state and have the STATUS as Running.

    • Issue the following command: 

      $ oc get pod -l app.kubernetes.io/component=collector -A

      You get an output similar to the following example: 

      NAMESPACE           NAME             READY   STATUS    RESTARTS   AGE
openshift-logging   instance-8f6r8   1/1     Running   0          13m
openshift-logging   instance-bbjxv   1/1     Running   0          13m
openshift-logging   instance-f6dkj   1/1     Running   0          13m
openshift-logging   instance-g28np   1/1     Running   0          13m
openshift-logging   instance-h4w2t   1/1     Running   0          13m
openshift-logging   instance-vh8tw   1/1     Running   0          13m

2.2.2. Checking update readiness of Loki Operator
Link kopieren

Before you update Loki Operator, ensure that there are no alerts listed and all pods run correctly. This check ensures a smooth update.

Prerequisites

  • You have installed Loki Operator v6.
  • You have administrator permissions.
  • You have access to the OpenShift Container Platform web console.
  • You have installed the OpenShift CLI (oc).

Procedure

  1. Verify that no alerts are listed for Loki Operator:

    1. Navigate to Observe > Alerting.

    2. Use this filter to check alerts: 

      Source: platform
Alert State: Firing
Label: namespace=openshift-logging

      Ensure that no upgrade-blocking alerts are listed.

  2. In the OpenShift CLI (oc), verify that all the pods have all the containers in the READY state and have the STATUS as Running.

    • Issue the following command: 

      $ oc get pods -l app.kubernetes.io/managed-by=lokistack-controller -n openshift-logging

      You get an output similar to the following example: 

      NAME                                          READY   STATUS    RESTARTS   AGE
logging-loki-compactor-0                      1/1     Running   0          18m
logging-loki-distributor-55dd9d9dd-bzbhg      1/1     Running   0          18m
logging-loki-distributor-55dd9d9dd-fvt56      1/1     Running   0          3m23s
logging-loki-gateway-cf7fb7479-jdr2t          2/2     Running   0          18m
logging-loki-gateway-cf7fb7479-qr7t9          2/2     Running   0          18m
logging-loki-index-gateway-0                  1/1     Running   0          18m
logging-loki-index-gateway-1                  1/1     Running   0          2m51s
logging-loki-ingester-0                       1/1     Running   0          18m
logging-loki-ingester-1                       1/1     Running   0          2m50s
logging-loki-ingester-2                       1/1     Running   0          15m
logging-loki-querier-5c4bf778b-hh24t          1/1     Running   0          18m
logging-loki-querier-5c4bf778b-nfzv6          1/1     Running   0          18m
logging-loki-query-frontend-f5f845489-5ztqd   1/1     Running   0          18m
logging-loki-query-frontend-f5f845489-wddw7   1/1     Running   0          18m

2.3. Updating OpenShift Logging by using the CLI
Link kopieren

You can update Logging for Red Hat OpenShift by using the CLI. You can follow the required sequence to update the Loki Operator and the Red Hat OpenShift Logging Operator.

2.3.1. Updating the Loki Operator by using the CLI
Link kopieren

To update the Loki Operator to a new version, change the update channel for the Operator subscription.

Prerequisites

  • You have checked readiness for update.
  • You have installed Loki Operator v6.
  • The Loki Operator version you are updating from is not more than two versions older than 6.5.0.
  • You have installed the OpenShift CLI (oc).

Procedure

  1. Find the name of the subscription for the Loki Operator by using the following command: 

    $ oc get subscription -n openshift-operators-redhat

    You get an output similar to the following example: 

    NAME            PACKAGE         SOURCE             CHANNEL
loki-operator   loki-operator   redhat-operators   stable-6.<y>

    Look for the value of PACKAGE listed for Loki Operator in the NAME column. The subscription name in the example output is loki-operator.

  2. Patch the subscription channel by using the following command: 

    $ oc patch subscription loki-operator -n openshift-operators-redhat \
    --type='merge' \
    -p '{"spec":{"channel":"<channel>"}}'

    Replace <channel> with the value stable-6.5.

    Important

    The maximum supported update channel is N+2 version, where N is your current version. For example, if you are updating from Logging 6.0, only select a maximum of stable-6.2 version as the update channel. Updating to a version that is more than two versions newer is not supported.

  3. Check whether the installPlanApproval value is set to Automatic or Manual.

    1. Find the install plan by using the following command: 

      $ oc get installplan -n openshift-operators-redhat

      You get an output similar to the following example: 

      NAME            CSV                    APPROVAL    APPROVED
install-mfvsm   loki-operator.v6.y.z   Automatic   true

    2. If the installPlanApproval value is set to Manual, approve the plan by using the following command: 

      $ oc patch installplan <plan_name> -n openshift-operators-redhat --type merge -p '{"spec":{"approved":true}}'

      Replace <plan_name> with the result obtained in the previous step.

Verification

  • Check the ClusterServiceVersion (CSV) in the namespace. 

    $ oc get csv -n openshift-operators-redhat | grep loki-operator

    You get an output similar to the following example: 

    NAME                     DISPLAY                     VERSION   REPLACES                 PHASE
loki-operator.v6.5.0     Loki Operator               6.5.0     loki-operator.v6.y.z     Succeeded

Next steps

  • Update the Red Hat OpenShift Logging Operator.

2.3.2. Updating the Red Hat OpenShift Logging Operator by using the CLI
Link kopieren

To update the Red Hat OpenShift Logging Operator to a new version, change the update channel for the Operator subscription.

Prerequisites

  • You have installed Red Hat OpenShift Logging Operator v6.
  • You have installed the OpenShift CLI (oc).
  • If you use Loki storage, ensure that you update Loki Operator first.

Procedure

  1. Find the name of the subscription for the Red Hat OpenShift Logging Operator by using the following command: 

    $ oc get subscription -n openshift-logging

    You get an output similar to the following example: 

    NAME              PACKAGE           SOURCE             CHANNEL
cluster-logging   cluster-logging   redhat-operators   stable-6.<y>

    Look for the value of PACKAGE listed for cluster-logging in the NAME column. The subscription name in the example output is cluster-logging.

  2. Patch the subscription channel by using the following command: 

    $ oc patch subscription <subscription_name> -n openshift-logging \
    --type='merge' \
    -p '{"spec":{"channel":"<channel>"}}'

    Replace <subscription_name> with the subscription name obtained in the previous step and <channel> with the value stable-6.5.

  3. Check whether the installPlanApproval value equals Automatic or Manual.

    1. Find the install plan by using the following command: 

      $ oc get installplan -n openshift-logging

      You get an output similar to the following example: 

      NAME            CSV                      APPROVAL    APPROVED
install-7cnnf   cluster-logging.v6.y.z   Automatic   true
install-gsmb4   cluster-logging.v6.y.z   Automatic   true

    2. If the installPlanApproval value is set to Manual, approve the plan by using the following command: 

      $ oc patch installplan <plan_name> -n openshift-logging --type merge -p '{"spec":{"approved":true}}'

      Replace <plan_name> with the result obtained in the previous step.

Verification

  • Check the ClusterServiceVersion (CSV) in the namespace. 

    $ oc get csv -n openshift-logging | grep cluster-logging

    You get an output similar to the following example: 

    NAME                     DISPLAY                     VERSION   REPLACES                 PHASE
cluster-logging.v6.5.0   Red Hat OpenShift Logging   6.5.0     cluster-logging.v6.y.z   Succeeded

2.4. Updating OpenShift Logging by using the web console
Link kopieren

You can update Logging for Red Hat OpenShift by using the web console. You can follow the required sequence to update the Loki Operator and the Red Hat OpenShift Logging Operator.

2.4.1. Updating the Loki Operator
Link kopieren

To update the Loki Operator to a new version, you must change the update channel for the Operator subscription.

Prerequisites

  • You have installed Loki Operator v6.
  • The Loki Operator version you are updating from is not more than two versions older than 6.5.0.
  • You have administrator permissions.
  • You have access to the OpenShift Container Platform web console.

Procedure

  1. Navigate to the list of installed Operators.

    • If your version of OpenShift Container Platform is 4.19 or earlier:

      Navigate to OpenShift Console > Administrator view > OperatorHub > Operators > Installed Operators.

    • If your version of OpenShift Container Platform is 4.20 or later:

      Navigate to OpenShift Console > Administrator view > Ecosystem > Software Catalog > Operators > Installed Operators.

  2. Select the openshift-operators-redhat project.
  3. Click the Loki Operator.
  4. Click Subscription.
  5. In the Subscription details section, click the Update channel link.

  6. In the Change Subscription Update Channel window, select the update channel, stable-6.5.

    Important

    The maximum supported update channel is N+2 version, where N is your current version. For example, if you are updating from Logging 6.0, only select a maximum of stable-6.2 version as the update channel. Updating to a version that is more than two versions newer is not supported.

    • If the Update approval field is set to Automatic, Click Save.

    • If the Update approval field is set to Manual, the Upgrade status displays Upgrade available. In this case, follow these steps:

      1. Click Upgrade available.
      2. Click Preview InstallPlan.
      3. Review the displayed install plan and click Approve.
  7. Wait for the operator to update.

  8. Navigate to the list of installed Operators.

    • If your version of OpenShift Container Platform is 4.19 or earlier:

      Navigate to OpenShift Console > Administrator view > OperatorHub > Operators > Installed Operators.

    • If your version of OpenShift Container Platform is 4.20 or later:

      Navigate to OpenShift Console > Administrator view > Ecosystem > Software Catalog > Operators > Installed Operators.

  9. Verify that the Loki Operator version matches the loki-operator.v6.5.0 version.
  10. On the Operators > Installed Operators page, wait for the Status field to report Succeeded.
  11. Check whether the LokiStack custom resource has the v13 schema version. If the v13 schema version is missing, add it.

2.4.2. Updating the Red Hat OpenShift Logging Operator
Link kopieren

To update the Red Hat OpenShift Logging Operator to a new minor version, change the update channel for the Operator subscription.

Prerequisites

  • You have installed Red Hat OpenShift Logging Operator v6.
  • You have administrator permissions.
  • You have access to the Red Hat OpenShift Logging web console.

Procedure

  1. Navigate to the list of installed Operators.

    • If your version of OpenShift Container Platform is 4.19 or earlier:

      Navigate to OpenShift Console > Administrator view > OperatorHub > Operators > Installed Operators.

    • If your version of OpenShift Container Platform is 4.20 or later:

      Navigate to OpenShift Console > Administrator view > Ecosystem > Software Catalog > Operators > Installed Operators.

  2. Select the openshift-logging project.
  3. Click the Red Hat OpenShift Logging Operator.
  4. Click Subscription.
  5. In the Subscription details section, click the Update channel link.

  6. In the Change Subscription Update Channel window, select the update channel, stable-6.5.

    • If the Update approval field is set to Automatic, Click Save.

    • If the Update approval field is set to Manual, the Upgrade status displays Upgrade available. In this case, follow these steps:

      1. Click Upgrade available.
      2. Click Preview InstallPlan.
      3. Review the displayed install plan and click Approve.

Verification

  1. Navigate to the list of installed Operators.

    • If your version of OpenShift Container Platform is 4.19 or earlier:

      Navigate to OpenShift Console > Administrator view > OperatorHub > Operators > Installed Operators.

    • If your version of OpenShift Container Platform is 4.20 or later:

      Navigate to OpenShift Console > Administrator view > Ecosystem > Software Catalog > Operators > Installed Operators.

  2. Wait for the Status field to report Succeeded.
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Legal Notice

Theme

© 2026 Red HatNach oben