This is a cache of https://docs.openshift.com/container-platform/4.5/service_mesh/v1x/removing-ossm.html. It is a snapshot of the page at 2024-11-21T00:25:17.107+0000.
Removing <strong>service</strong> Mesh - <strong>service</strong> Mesh 1.x | <strong>service</strong> Mesh | OpenShift Container Platform 4.5
    Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
    2. history
×

Removing Red Hat OpenShift service Mesh

This process allows you to remove Red Hat OpenShift service Mesh from an existing OpenShift Container Platform instance. Remove the control plane before removing the operators.

Removing the Red Hat OpenShift service Mesh member roll

The serviceMeshMemberRoll resource is automatically deleted when you delete the serviceMeshControlPlane resource it is associated with.

Removing the Red Hat OpenShift service Mesh control plane

You can remove the service Mesh control plane by using the OpenShift Container Platform web console or the CLI.

Removing the control plane with the web console

Follow this procedure to remove the Red Hat OpenShift service Mesh control plane by using the web console.

Prerequisites

  • The Red Hat OpenShift service Mesh control plane must be deployed.

Procedure

  1. Log in to the OpenShift Container Platform web console.

  2. Click the Project menu and choose the istio-system project from the list.

  3. Navigate to Operators → Installed Operators.

  4. Click on service Mesh Control Plane under Provided APIs.

  5. Click the serviceMeshControlPlane menu kebab.

  6. Click Delete service Mesh Control Plane.

  7. Click Delete on the confirmation dialog window to remove the serviceMeshControlPlane.

Removing the control plane from the CLI

Follow this procedure to remove the Red Hat OpenShift service Mesh control plane by using the CLI.

Prerequisites

  • The Red Hat OpenShift service Mesh control plane must be deployed.

  • Access to the OpenShift Container Platform Command-line Interface (CLI) also known as oc.

Procedure

When you remove the serviceMeshControlPlane, service Mesh tells the Operator to begin uninstalling everything it installed.

You can use the shortened smcp alias in place of servicemeshcontrolplane.

  1. Log in to the OpenShift Container Platform CLI.

  2. Run this command to retrieve the name of the installed serviceMeshControlPlane:

    $ oc get servicemeshcontrolplanes -n istio-system

  3. Replace <name_of_custom_resource> with the output from the previous command, and run this command to remove the custom resource:

    $ oc delete servicemeshcontrolplanes -n istio-system <name_of_custom_resource>

Removing the installed Operators

You must remove the Operators to successfully remove Red Hat OpenShift service Mesh. Once you remove the Red Hat OpenShift service Mesh Operator, you must remove the Kiali Operator, the Jaeger Operator, and the Elasticsearch Operator.

Removing the Red Hat OpenShift service Mesh Operator

Follow this procedure to remove the Red Hat OpenShift service Mesh Operator.

Prerequisites

  • Access to the OpenShift Container Platform web console.

  • The Red Hat OpenShift service Mesh Operator must be installed.

Procedure

  1. Log in to the OpenShift Container Platform web console.

  2. From the Operators → Installed Operators page, scroll or type a keyword into the Filter by name to find the Red Hat OpenShift service Mesh Operator. Then, click on it.

  3. On the right-hand side of the Operator Details page, select Uninstall Operator from the Actions drop-down menu.

  4. 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.

Removing the Kiali Operator

Follow this procedure to remove the Kiali Operator.

Prerequisites

  • Access to the OpenShift Container Platform web console.

  • The Kiali Operator must be installed.

Procedure

  1. Log in to the OpenShift Container Platform web console.

  2. 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.

  3. On the right-hand side of the Operator Details page, select Uninstall Operator from the Actions drop-down menu.

  4. 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.

Removing the Jaeger Operator

Follow this procedure to remove the Jaeger Operator.

Prerequisites

  • Access to the OpenShift Container Platform web console.

  • The Jaeger Operator must be installed.

Procedure

  1. Log in to the OpenShift Container Platform web console.

  2. 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.

  3. On the right-hand side of the Operator Details page, select Uninstall Operator from the Actions drop-down menu.

  4. 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.

Removing the Elasticsearch Operator

Follow this procedure to remove the Elasticsearch Operator.

Prerequisites

  • Access to the OpenShift Container Platform web console.

  • The Elasticsearch Operator must be installed.

Procedure

  1. Log in to the OpenShift Container Platform web console.

  2. 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.

  3. On the right-hand side of the Operator Details page, select Uninstall Operator from the Actions drop-down menu.

  4. 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.

Clean up Operator resources

Follow this procedure to manually remove resources left behind after removing the Red Hat OpenShift service Mesh Operator using the OpenShift console.

Prerequisites

  • An account with cluster administration access.

  • Access to the OpenShift Container Platform Command-line Interface (CLI) also known as oc.

Procedure

  1. Log in to the OpenShift Container Platform CLI as a cluster administrator.

  2. 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.

    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 Red Hat OpenShift service Mesh Operator was installed.

    		 
    $ oc delete validatingwebhookconfiguration/openshift-operators.servicemesh-resources.maistra.io
    $ oc delete mutatingwebhookconfigurations/openshift-operators.servicemesh-resources.maistra.io
    $ oc delete -n openshift-operators daemonset/istio-node
    $ oc delete clusterrole/istio-admin clusterrole/istio-cni clusterrolebinding/istio-cni
    $ oc delete clusterrole istio-view istio-edit
    $ oc delete clusterrole jaegers.jaegertracing.io-v1-admin jaegers.jaegertracing.io-v1-crdview jaegers.jaegertracing.io-v1-edit jaegers.jaegertracing.io-v1-view
    $ 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
    $ oc get crds -o name | grep '.*\.kiali\.io' | xargs -r -n 1 oc delete
    $ oc delete crds jaegers.jaegertracing.io
    $ oc delete svc admission-controller -n <operator-project>
    $ oc delete project <istio-system-project>