// Module included in the following assemblies:
//
// * observability/logging/cluster-logging-uninstall.adoc

:_mod-docs-content-type: PROCEDURE
[id="uninstall-cluster-logging-operator_{context}"]
= Uninstalling the {logging}

You can stop aggregating logs by deleting the {clo} and the `ClusterLogging` custom resource (CR).

.Prerequisites

* Have access to the {product-title} web console as a user with `cluster-admin` privileges.

.Procedure

. Go to the *Administration* -> *Custom Resource Definitions* page, and click *ClusterLogging*.

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

. Click the Options menu {kebab} next to the instance, and click *Delete ClusterLogging*.

. Go to the *Administration* -> *Custom Resource Definitions* page.

. Click the Options menu {kebab} next to *ClusterLogging*, and select *Delete Custom Resource Definition*.
+
[WARNING]
====
Deleting the `ClusterLogging` CR does not remove the persistent volume claims (PVCs). To delete the remaining PVCs, persistent volumes (PVs), and associated data, you must take further action. Releasing or deleting PVCs can delete PVs and cause data loss.
====

. If you have created a `ClusterLogForwarder` CR, click the Options menu {kebab} next to *ClusterLogForwarder*, and then click *Delete Custom Resource Definition*.

. Go to the *Ecosystem* -> *Installed Operators* page.

. Click the Options menu {kebab} next to the {clo}, and then click *Uninstall Operator*.

. Optional: Delete the `openshift-logging` project.
+
[WARNING]
====
Deleting the `openshift-logging` project deletes everything in that namespace, including any persistent volume claims (PVCs). If you want to preserve logging data, do not delete the `openshift-logging` project.
====

.. Go to the *Home* -> *Projects* page.
.. Click the Options menu {kebab} next to the *openshift-logging* project, and then click *Delete Project*.
.. Confirm the deletion by typing `openshift-logging` in the dialog box, and then click *Delete*.
