Skip to content

Commit 9613129

Browse files
committed
Uninstall cluster-logging from OCP leaves behind cluster-logging operator and elastic-search operator
1 parent a4c253d commit 9613129

File tree

1 file changed

+50
-13
lines changed

1 file changed

+50
-13
lines changed

modules/cluster-logging-uninstall.adoc

Lines changed: 50 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
[id="cluster-logging-uninstall_{context}"]
66
= Uninstalling cluster logging from {product-title}
77

8-
You can remove cluster logging from your cluster.
8+
You can stop log aggregation by deleting the Cluster Logging custom resource (CR). However, after deleting the CR there are other cluster logging components that remain, which you can optionally remove.
99

1010
.Prerequisites
1111

@@ -15,17 +15,54 @@ You can remove cluster logging from your cluster.
1515

1616
To remove cluster logging:
1717

18-
. Use the following command to remove everything generated during the deployment.
19-
+
20-
[source,terminal]
21-
----
22-
$ oc delete clusterlogging instance -n openshift-logging
23-
----
18+
. Use the {product-title} web console to remove the Cluster Logging CR:
19+
20+
.. Switch to the *Administration* -> *Custom Resource Definitions* page.
21+
22+
.. On the *Custom Resource Definitions* page, click *ClusterLogging*.
23+
24+
.. On the *Custom Resource Definition Details* page, click *Instances*.
25+
26+
.. Click the Options menu {kebab} next to the instance and select *Delete ClusterLogging*.
27+
28+
. Optional: Delete the custom resource definitions (CRD):
29+
30+
.. Switch to the *Administration* -> *Custom Resource Definitions* page.
31+
32+
.. Click the Options menu {kebab} next to *ClusterLogForwarder* and select *Delete Custom Resource Definition*.
33+
34+
.. Click the Options menu {kebab} next to *ClusterLogging* and select *Delete Custom Resource Definition*.
35+
36+
.. Click the Options menu {kebab} next to *Elasticsearch* and select *Delete Custom Resource Definition*.
37+
38+
. Optional: Remove the Cluster Logging Operator and Elasticsearch Operator:
39+
40+
.. Switch to the *Operators* -> *Installed Operators* page.
2441

25-
. Use the following command to remove the Persistent Volume Claims that remain
26-
after the Operator instances are deleted:
42+
.. Click the Options menu {kebab} next to the Cluster Logging Operator and select *Uninstall Operator*.
43+
44+
.. Click the Options menu {kebab} next to the Elasticsearch Operator and select *Uninstall Operator*.
45+
46+
. Optional: Remove the Cluster Logging and Elasticsearch projects.
47+
48+
.. Switch to the *Home* -> *Projects* page.
49+
50+
.. Click the Options menu {kebab} next to the *openshift-logging* project and select *Delete Project*.
51+
52+
.. Confirm the deletion by typing `openshift-logging` in the dialog box and click *Delete*.
53+
54+
.. Click the Options menu {kebab} next to the *openshift-operators-redhat* project and select *Delete Project*.
2755
+
28-
[source,terminal]
29-
----
30-
$ oc delete pvc --all -n openshift-logging
31-
----
56+
[IMPORTANT]
57+
====
58+
Do not delete the `openshift-operators-redhat` project if other global operators are installed in this namespace.
59+
====
60+
61+
.. Confirm the deletion by typing `openshift-operators-redhat` in the dialog box and click *Delete*.
62+
63+
. Optional: Remove any Cluster Logging persistent volume claims (PVC):
64+
65+
.. Switch to the *Storage* -> *Persistent Volume Claims* page.
66+
67+
.. Click the Options menu {kebab} next to each PVC and select *Delete Persistent Volume Claim*.
68+

0 commit comments

Comments
 (0)