$ oc get subscription.operators.coreos.com serverless-operator -n openshift-serverless -o yaml | grep currentCSV
You can remove the logging subsystem from your OKD cluster.
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.
The Red Hat OpenShift Logging Operator and Elasticsearch Operator are installed.
Use the
OKD web console
to remove the ClusterLogging
CR:
Switch to the Administration → Custom Resource Definitions page.
On the Custom Resource Definitions page, click ClusterLogging.
On the Custom Resource Definition Details page, click Instances.
Click the Options menu next to the instance and select Delete ClusterLogging.
Optional: Delete the custom resource definitions (CRD):
Switch to the Administration → Custom Resource Definitions page.
Click the Options menu next to ClusterLogForwarder and select Delete Custom Resource Definition.
Click the Options menu next to ClusterLogging and select Delete Custom Resource Definition.
Click the Options menu next to Elasticsearch and select Delete Custom Resource Definition.
Optional: Remove the Red Hat OpenShift Logging Operator and Elasticsearch Operator:
Switch to the Operators → Installed Operators page.
Click the Options menu next to the Red Hat OpenShift Logging Operator and select Uninstall Operator.
Click the Options menu next to the Elasticsearch Operator and select Uninstall Operator.
Optional: Remove the openshift-logging
and openshift-operators-redhat
projects.
Do not delete the |
Switch to the Home → Projects page.
Click the Options menu next to the openshift-logging project and select Delete Project.
Confirm the deletion by typing openshift-logging
in the dialog box and click Delete.
Click the Options menu next to the openshift-operators-redhat project and select Delete Project.
Confirm the deletion by typing openshift-operators-redhat
in the dialog box and click Delete.
To keep the PVCs for reuse with other pods, keep the labels or PVC names that you need to reclaim the PVCs.
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. |
Switch to the Storage → Persistent Volume Claims page.
Click the Options menu next to each PVC and select Delete Persistent Volume Claim.
If you want to recover storage space, you can delete the PVs.
Cluster administrators can delete installed Operators from a selected namespace by using the web console.
You have access to an OKD cluster web console using an account with
cluster-admin
permissions.
Navigate to the Operators → Installed Operators page.
Scroll or enter a keyword into the Filter by name field to find the Operator that you want to remove. Then, click on it.
On the right side of the Operator Details page, select Uninstall Operator from the Actions list.
An Uninstall Operator? dialog box is displayed.
Select Uninstall to remove the Operator, Operator deployments, and pods. Following this action, the Operator stops running and no longer receives updates.
This action does not remove resources managed by the Operator, including custom resource definitions (CRDs) and custom resources (CRs). Dashboards and navigation items enabled by the web console and off-cluster resources that continue to run might need manual clean up. To remove these after uninstalling the Operator, you might need to manually delete the Operator CRDs. |
Cluster administrators can delete installed Operators from a selected namespace by using the CLI.
Access to an OKD cluster using an account with
cluster-admin
permissions.
oc
command installed on workstation.
Ensure the latest version of the subscribed operator (for example, serverless-operator
) is identified in the currentCSV
field.
$ oc get subscription.operators.coreos.com serverless-operator -n openshift-serverless -o yaml | grep currentCSV
currentCSV: serverless-operator.v1.28.0
Delete the subscription (for example, serverless-operator
):
$ oc delete subscription.operators.coreos.com serverless-operator -n openshift-serverless
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
clusterserviceversion.operators.coreos.com "serverless-operator.v1.28.0" deleted