Chapter 16. Uninstalling Logging
You can remove logging from your OpenShift Container Platform cluster by removing installed Operators and related custom resources (CRs).
16.1. Uninstalling the logging
You can stop aggregating logs by deleting the Red Hat OpenShift Logging Operator and the ClusterLogging
custom resource (CR).
Prerequisites
- You have administrator permissions.
- You have access to the Administrator perspective of the OpenShift Container Platform web console.
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 next to the instance, and click Delete ClusterLogging.
-
Go to the Administration
Custom Resource Definitions page. Click the options menu next to ClusterLogging, and select Delete Custom Resource Definition.
WarningDeleting 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 next to ClusterLogForwarder, and then click Delete Custom Resource Definition. -
Go to the Operators
Installed Operators page. - Click the options menu next to the Red Hat OpenShift Logging Operator, and then click Uninstall Operator.
Optional: Delete the
openshift-logging
project.WarningDeleting 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 theopenshift-logging
project.-
Go to the Home
Projects page. - Click the options menu 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.
-
Go to the Home
16.2. Deleting logging PVCs
To keep persistent volume claims (PVCs) for reuse with other pods, keep the labels or PVC names that you need to reclaim the PVCs. If you do not want to keep the PVCs, you can delete them. If you want to recover storage space, you can also delete the persistent volumes (PVs).
Prerequisites
- You have administrator permissions.
- You have access to the Administrator perspective of the OpenShift Container Platform web console.
Procedure
-
Go to the Storage
Persistent Volume Claims page. - Click the options menu next to each PVC, and select Delete Persistent Volume Claim.
16.3. Uninstalling Loki
Prerequisites
- You have administrator permissions.
- You have access to the Administrator perspective of the OpenShift Container Platform web console.
-
If you have not already removed the Red Hat OpenShift Logging Operator and related resources, you have removed references to LokiStack from the
ClusterLogging
custom resource.
Procedure
-
Go to the Administration
Custom Resource Definitions page, and click LokiStack. - On the Custom Resource Definition Details page, click Instances.
- Click the options menu next to the instance, and then click Delete LokiStack.
-
Go to the Administration
Custom Resource Definitions page. - Click the options menu next to LokiStack, and select Delete Custom Resource Definition.
- Delete the object storage secret.
-
Go to the Operators
Installed Operators page. - Click the options menu next to the Loki Operator, and then click Uninstall Operator.
Optional: Delete the
openshift-operators-redhat
project.ImportantDo not delete the
openshift-operators-redhat
project if other global Operators are installed in this namespace.-
Go to the Home
Projects page. - Click the options menu next to the openshift-operators-redhat project, and then click Delete Project.
-
Confirm the deletion by typing
openshift-operators-redhat
in the dialog box, and then click Delete.
-
Go to the Home
16.4. Uninstalling Elasticsearch
Prerequisites
- You have administrator permissions.
- You have access to the Administrator perspective of the OpenShift Container Platform web console.
-
If you have not already removed the Red Hat OpenShift Logging Operator and related resources, you must remove references to Elasticsearch from the
ClusterLogging
custom resource.
Procedure
-
Go to the Administration
Custom Resource Definitions page, and click Elasticsearch. - On the Custom Resource Definition Details page, click Instances.
- Click the options menu next to the instance, and then click Delete Elasticsearch.
-
Go to the Administration
Custom Resource Definitions page. - Click the options menu next to Elasticsearch, and select Delete Custom Resource Definition.
- Delete the object storage secret.
-
Go to the Operators
Installed Operators page. - Click the options menu next to the OpenShift Elasticsearch Operator, and then click Uninstall Operator.
Optional: Delete the
openshift-operators-redhat
project.ImportantDo not delete the
openshift-operators-redhat
project if other global Operators are installed in this namespace.-
Go to the Home
Projects page. - Click the options menu next to the openshift-operators-redhat project, and then click Delete Project.
-
Confirm the deletion by typing
openshift-operators-redhat
in the dialog box, and then click Delete.
-
Go to the Home
16.5. Deleting Operators from a cluster using the CLI
Cluster administrators can delete installed Operators from a selected namespace by using the CLI.
Prerequisites
-
You have access to an OpenShift Container Platform cluster using an account with
cluster-admin
permissions. -
The OpenShift CLI (
oc
) is installed on your workstation.
Procedure
Ensure the latest version of the subscribed operator (for example,
serverless-operator
) is identified in thecurrentCSV
field.$ oc get subscription.operators.coreos.com serverless-operator -n openshift-serverless -o yaml | grep currentCSV
Example output
currentCSV: serverless-operator.v1.28.0
Delete the subscription (for example,
serverless-operator
):$ oc delete subscription.operators.coreos.com serverless-operator -n openshift-serverless
Example output
subscription.operators.coreos.com "serverless-operator" deleted
Delete the CSV for the Operator in the target namespace using the
currentCSV
value from the previous step:$ oc delete clusterserviceversion serverless-operator.v1.28.0 -n openshift-serverless
Example output
clusterserviceversion.operators.coreos.com "serverless-operator.v1.28.0" deleted
Additional resources