Skip to content

Commit 785635f

Browse files
authored
Merge pull request #36673 from michaelryanpeter/OSDOCS-1922_client_deletion_of_OLM_operators
OSDOCS-1922: OLM-1733 Client deletion of operands for OLM Operators
2 parents 272ba3e + 8993e6b commit 785635f

File tree

1 file changed

+15
-11
lines changed

1 file changed

+15
-11
lines changed

modules/olm-deleting-operators-from-a-cluster-using-web-console.adoc

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -19,19 +19,23 @@ endif::[]
1919

2020
.Procedure
2121

22-
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into the *Filter by name* to find the Operator you want. Then, click on it.
22+
. From the *Operators* → *Installed Operators* page, scroll or enter a keyword into the *Filter by name* field to find the Operator you want. Then, click on it.
2323

24-
. On the right-hand side of the *Operator Details* page, select *Uninstall Operator* from the *Actions* drop-down menu.
24+
. On the right side of the *Operator Details* page, select *Uninstall Operator* from the *Actions* drop-down menu.
2525
+
26-
An *Uninstall Operator?* dialog box is displayed, alerting you that:
26+
An *Uninstall Operator?* dialog box opens, listing the Operands associated with the Operator.
2727
+
28-
[.small]
29-
--
30-
*Operator VerticalPodAutoscaler will be removed from openshift-vertical-pod-autoscaler. Click on the checkbox below to also remove all Operands associated with this Operator. If your Operator configured off-cluster resources, these will continue to run and require manual cleanup.*
31-
--
32-
+
33-
Any resources managed by the Operator, including CRDs and CRs, are not removed. The web console enables dashboards and navigation items for some Operators. To remove these after uninstalling the Operator, you might need to manually delete the Operator CRDs.
28+
. Choose one of the following options for the *Delete all operand instances for this Operator* checkbox:
29+
30+
* To remove Operands managed by the Operator automatically, including custom resources (CRs), select the checkbox.
31+
* To keep the Operands in place or remove them manually later, leave the checkbox clear.
32+
. Select *Uninstall* to remove the Operator, any Operator deployments, and pods. This Operator stops running and no longer receives updates.
33+
34+
.Verification
3435

35-
. Optional: To remove all operands associated with the Operator, select *Delete all operand instances for this operator* checkbox.
36+
- If you choose to remove Operands managed by the Operator automatically, the *Uninstall Operator?* dialog box confirms if the uninstall process is a success. If there are errors, the dialog lists the Operands that you need to delete manually.
3637

37-
. Select *Uninstall*. This Operator stops running and no longer receives updates.
38+
[NOTE]
39+
====
40+
Dashboards and navigation items enabled by the web console and off-cluster resources that continue to run might need manual clean up.
41+
====

0 commit comments

Comments
 (0)