1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/ossm-operatorhub-remove.adoc
Ashley Hardin e44ecfd4c6 Applied changes based on OperatorHub UI updates
Conflicts:
	modules/dedicated-efk-install-deploy.adoc
	modules/efk-logging-deploy-subscription.adoc
2019-09-12 15:27:42 -04:00

145 lines
5.0 KiB
Plaintext

// Module included in the following assemblies:
//
// * service_mesh/service_mesh_install/removing-ossm.adoc
[id="ossm-operatorhub-remove_{context}"]
= Removing the installed Operators
You must remove the Operators to successfully remove {ProductName}. Once you
remove the {ProductName} Operator, you must remove the Jaeger Operator, Kiali
Operator, and the Elasticsearch Operator.
[id="ossm-remove-operator-servicemesh_{context}"]
== Removing the {ProductName} Operator
Follow this procedure to remove the {ProductName} Operator.
.Prerequisites
* Access to the {product-title} web console.
* The {ProductName} Operator must be installed.
.Procedure
. Log in to the {product-title} web console.
. 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.
. On the right-hand side of the *Operator Details* page, select *Uninstall
Operator* from the *Actions* drop-down menu.
. When prompted by the *Remove Operator Subscription* window, optionally select the
*Also completely remove the Operator from the selected namespace*
check box if you want all components related to the installation to be removed.
This removes the CSV, which in turn removes the Pods, Deployments, CRDs, and CRs
associated with the Operator.
[id="ossm-remove-operator-jaeger_{context}"]
== Removing the Jaeger Operator
Follow this procedure to remove the Jaeger Operator.
.Prerequisites
* Access to the {product-title} web console.
* The Jaeger Operator must be installed.
.Procedure
. Log in to the {product-title} web console.
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into
the *Filter by name* to find the Jaeger Operator. Then, click on it.
. On the right-hand side of the *Operator Details* page, select *Uninstall
Operator* from the *Actions* drop-down menu.
. When prompted by the *Remove Operator Subscription* window, optionally select the
*Also completely remove the Operator from the selected namespace*
check box if you want all components related to the installation to be removed.
This removes the CSV, which in turn removes the Pods, Deployments, CRDs, and CRs
associated with the Operator.
[id="ossm-remove-operator-kiali_{context}"]
== Removing the Kiali Operator
Follow this procedure to remove the Kiali Operator.
.Prerequisites
* Access to the {product-title} web console.
* The Kiali Operator must be installed.
.Procedure
. Log in to the {product-title} web console.
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into
the *Filter by name* to find the Kiali Operator. Then, click on it.
. On the right-hand side of the *Operator Details* page, select *Uninstall
Operator* from the *Actions* drop-down menu.
. When prompted by the *Remove Operator Subscription* window, optionally select the
*Also completely remove the Operator from the selected namespace*
check box if you want all components related to the installation to be removed.
This removes the CSV, which in turn removes the Pods, Deployments, CRDs, and CRs
associated with the Operator.
[id="ossm-remove-operator-elasticsearch_{context}"]
== Removing the Elasticsearch Operator
Follow this procedure to remove the Elasticsearch Operator.
.Prerequisites
* Access to the {product-title} web console.
* The Elasticsearch Operator must be installed.
.Procedure
. Log in to the {product-title} web console.
. From the *Operators* → *Installed Operators* page, scroll or type a keyword into
the *Filter by name* to find the Elasticsearch Operator. Then, click on it.
. On the right-hand side of the *Operator Details* page, select *Uninstall
Operator* from the *Actions* drop-down menu.
. When prompted by the *Remove Operator Subscription* window, optionally select the
*Also completely remove the Operator from the selected namespace*
check box if you want all components related to the installation to be removed.
This removes the CSV, which in turn removes the Pods, Deployments, CRDs, and CRs
associated with the Operator.
[id="ossm-remove-cleanup_{context}"]
== Clean up Operator resources
Follow this procedure to manually remove resources left behind after removing the {ProductName} Operator by using the OperatorHub interface.
.Prerequisites
* An account with cluster administration access.
* Access to the {product-title} Command-line Interface (CLI) also known as `oc`.
.Procedure
. Log in to the {product-title} CLI as a cluster administrator.
. Run the following commands to clean up resources after uninstalling the Operators:
+
[NOTE]
====
Replace `<operator-project>` with the name of the project where the {ProductName} Operator was installed. This is typically `openshift-operators`.
====
+
----
$ oc delete validatingwebhookconfiguration/<operator-project>.servicemesh-resources.maistra.io
$ oc delete -n <operator-project> daemonset/istio-node
$ oc delete clusterrole/istio-admin
$ oc get crds -o name | grep '.*\.istio\.io' | xargs -r -n 1 oc delete
$ oc get crds -o name | grep '.*\.maistra\.io' | xargs -r -n 1 oc delete
----