You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow this procedure to manually remove resources left behind after removing the {ProductName} Operator using the OpenShift console.
10
+
11
+
.Prerequisites
12
+
13
+
* An account with cluster administration access.
14
+
* Access to the {product-title} Command-line Interface (CLI) also known as `oc`.
15
+
16
+
.Procedure
17
+
18
+
. Log in to the {product-title} CLI as a cluster administrator.
19
+
20
+
. Run the following commands to clean up resources after uninstalling the Operators. If you intend to keep using Jaeger as a stand alone service without service mesh, do not delete the Jaeger resources.
21
+
+
22
+
[NOTE]
23
+
====
24
+
The Operators are installed in the `openshift-operators` namespace by default. If you installed the Operators in another namespace, replace `openshift-operators` with the name of the project where the {ProductName} Operator was installed.
Follow this procedure to manually remove resources left behind after removing the {ProductName} Operator using the OpenShift console.
10
+
11
+
.Prerequisites
12
+
13
+
* An account with cluster administration access.
14
+
* Access to the {product-title} Command-line Interface (CLI) also known as `oc`.
15
+
16
+
.Procedure
17
+
18
+
. Log in to the {product-title} CLI as a cluster administrator.
19
+
20
+
. Run the following commands to clean up resources after uninstalling the Operators. If you intend to keep using Jaeger as a stand alone service without service mesh, do not delete the Jaeger resources.
21
+
+
22
+
[NOTE]
23
+
====
24
+
The Operators are installed in the `openshift-operators` namespace by default. If you installed the Operators in another namespace, replace `openshift-operators` with the name of the project where the {ProductName} Operator was installed.
You must remove the Operators to successfully remove {ProductName}. Once you
10
-
remove the {ProductName} Operator, you must remove the Jaeger Operator, Kiali
11
-
Operator, and the Elasticsearch Operator.
9
+
You must remove the Operators to successfully remove {ProductName}. Once you remove the {ProductName} Operator, you must remove the Kiali Operator, the Jaeger Operator, and the Elasticsearch Operator.
12
10
13
11
[id="ossm-remove-operator-servicemesh_{context}"]
14
12
== Removing the {ProductName} Operator
@@ -24,35 +22,31 @@ Follow this procedure to remove the {ProductName} Operator.
24
22
25
23
. Log in to the {product-title} web console.
26
24
27
-
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into
28
-
the *Filter by name* to find the {ProductName} Operator. Then, click on it.
25
+
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into the *Filter by name* to find the {ProductName} Operator. Then, click on it.
29
26
30
-
. On the right-hand side of the *Operator Details* page, select *Uninstall
31
-
Operator* from the *Actions* drop-down menu.
27
+
. On the right-hand side of the *Operator Details* page, select *Uninstall Operator* from the *Actions* drop-down menu.
32
28
33
29
. When prompted by the *Remove Operator Subscription* window, optionally select the
34
30
*Also completely remove the Operator from the selected namespace*
35
31
check box if you want all components related to the installation to be removed.
36
-
This removes the CSV, which in turn removes the pods, Deployments, CRDs, and CRs
37
-
associated with the Operator.
32
+
This removes the CSV, which in turn removes the pods, Deployments, CRDs, and CRs associated with the Operator.
38
33
34
+
[id="ossm-remove-operator-kiali_{context}"]
35
+
== Removing the Kiali Operator
39
36
40
-
[id="ossm-remove-operator-jaeger_{context}"]
41
-
== Removing the Jaeger Operator
42
-
43
-
Follow this procedure to remove the Jaeger Operator.
37
+
Follow this procedure to remove the Kiali Operator.
44
38
45
39
.Prerequisites
46
40
47
41
* Access to the {product-title} web console.
48
-
* The Jaeger Operator must be installed.
42
+
* The Kiali Operator must be installed.
49
43
50
44
.Procedure
51
45
52
46
. Log in to the {product-title} web console.
53
47
54
48
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into
55
-
the *Filter by name* to find the Jaeger Operator. Then, click on it.
49
+
the *Filter by name* to find the Kiali Operator. Then, click on it.
56
50
57
51
. On the right-hand side of the *Operator Details* page, select *Uninstall
58
52
Operator* from the *Actions* drop-down menu.
@@ -63,22 +57,22 @@ check box if you want all components related to the installation to be removed.
63
57
This removes the CSV, which in turn removes the pods, Deployments, CRDs, and CRs
64
58
associated with the Operator.
65
59
66
-
[id="ossm-remove-operator-kiali_{context}"]
67
-
== Removing the Kiali Operator
60
+
[id="ossm-remove-operator-jaeger_{context}"]
61
+
== Removing the Jaeger Operator
68
62
69
-
Follow this procedure to remove the Kiali Operator.
63
+
Follow this procedure to remove the Jaeger Operator.
70
64
71
65
.Prerequisites
72
66
73
67
* Access to the {product-title} web console.
74
-
* The Kiali Operator must be installed.
68
+
* The Jaeger Operator must be installed.
75
69
76
70
.Procedure
77
71
78
72
. Log in to the {product-title} web console.
79
73
80
74
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into
81
-
the *Filter by name* to find the Kiali Operator. Then, click on it.
75
+
the *Filter by name* to find the Jaeger Operator. Then, click on it.
82
76
83
77
. On the right-hand side of the *Operator Details* page, select *Uninstall
84
78
Operator* from the *Actions* drop-down menu.
@@ -114,59 +108,3 @@ Operator* from the *Actions* drop-down menu.
114
108
check box if you want all components related to the installation to be removed.
115
109
This removes the CSV, which in turn removes the pods, Deployments, CRDs, and CRs
116
110
associated with the Operator.
117
-
118
-
[id="ossm-remove-cleanup_{context}"]
119
-
== Clean up Operator resources
120
-
121
-
Follow this procedure to manually remove resources left behind after removing the {ProductName} Operator by using the OperatorHub interface.
122
-
123
-
.Prerequisites
124
-
125
-
* An account with cluster administration access.
126
-
* Access to the {product-title} Command-line Interface (CLI) also known as `oc`.
127
-
128
-
.Procedure
129
-
130
-
. Log in to the {product-title} CLI as a cluster administrator.
131
-
132
-
. Run the following commands to clean up resources after uninstalling the Operators:
133
-
+
134
-
[NOTE]
135
-
====
136
-
Replace `<operator-project>` with the name of the project where the {ProductName} Operator was installed. This is typically `openshift-operators`.
0 commit comments