This is a cache of https://docs.okd.io/4.10/logging/cluster-logging-uninstall.html. It is a snapshot of the page at 2024-11-21T22:25:59.373+0000.
Uninstalling <strong>logging</strong> | <strong>logging</strong> | OKD 4.10
  1. Documentation
×

Uninstalling OpenShift logging

You can remove the logging subsystem from your OKD cluster.

Uninstalling the logging subsystem for Red Hat OpenShift

You can stop log aggregation by deleting the Clusterlogging custom resource (CR). After deleting the CR, there are other logging subsystem components that remain, which you can optionally remove.

Deleting the Clusterlogging CR does not remove the persistent volume claims (PVCs). To preserve or delete the remaining PVCs, persistent volumes (PVs), and associated data, you must take further action.

Prerequisites

  • The Red Hat OpenShift logging and Elasticsearch Operators must be installed.

Procedure

To remove OpenShift logging:

  1. Use the OKD web console to remove the Clusterlogging CR:

    1. Switch to the Administration → Custom Resource Definitions page.

    2. On the Custom Resource Definitions page, click Clusterlogging.

    3. On the Custom Resource Definition Details page, click Instances.

    4. Click the Options menu kebab next to the instance and select Delete Clusterlogging.

  2. Optional: Delete the custom resource definitions (CRD):

    1. Switch to the Administration → Custom Resource Definitions page.

    2. Click the Options menu kebab next to ClusterLogForwarder and select Delete Custom Resource Definition.

    3. Click the Options menu kebab next to Clusterlogging and select Delete Custom Resource Definition.

    4. Click the Options menu kebab next to Elasticsearch and select Delete Custom Resource Definition.

  3. Optional: Remove the Red Hat OpenShift logging Operator and OpenShift Elasticsearch Operator:

    1. Switch to the Operators → Installed Operators page.

    2. Click the Options menu kebab next to the Red Hat OpenShift logging Operator and select Uninstall Operator.

    3. Click the Options menu kebab next to the OpenShift Elasticsearch Operator and select Uninstall Operator.

  4. Optional: Remove the OpenShift logging and Elasticsearch projects.

    1. Switch to the Home → Projects page.

    2. Click the Options menu kebab next to the openshift-logging project and select Delete Project.

    3. Confirm the deletion by typing openshift-logging in the dialog box and click Delete.

    4. Click the Options menu kebab next to the openshift-operators-redhat project and select Delete Project.

      Do not delete the openshift-operators-redhat project if other global operators are installed in this namespace.

    5. Confirm the deletion by typing openshift-operators-redhat in the dialog box and click Delete.

  5. To keep the PVCs for reuse with other pods, keep the labels or PVC names that you need to reclaim the PVCs.

  6. Optional: If you do not want to keep the PVCs, you can delete them.

    Releasing or deleting PVCs can delete PVs and cause data loss.

    1. Switch to the Storage → Persistent Volume Claims page.

    2. Click the Options menu kebab next to each PVC and select Delete Persistent Volume Claim.

    3. If you want to recover storage space, you can delete the PVs.

Additional resources