This is a cache of https://docs.openshift.com/container-platform/4.6/service_mesh/v2x/removing-ossm.html. It is a snapshot of the page at 2024-11-22T23:51:20.184+0000.
Uninstalling Service Mesh - Service Mesh 2.x | Service Mesh | OpenShift Container Platform 4.6
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Uninstalling Service Mesh

To uninstall Red Hat OpenShift Service Mesh from an existing OpenShift Container Platform instance and remove its resources, you must delete the control plane, delete the Operators, and run commands to manually remove some resources.

Removing the Red Hat OpenShift Service Mesh control plane

To uninstall Service Mesh from an existing OpenShift Container Platform instance, first you delete the Service Mesh control plane and the Operators. Then, you run commands to remove residual resources.

Removing the Service Mesh control plane using the web console

You can remove the Red Hat OpenShift Service Mesh control plane by using the web console.

Procedure

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

  2. click the Project menu and select the project where you installed the Service Mesh control plane, for example istio-system.

  3. Navigate to Operators → Installed Operators.

  4. click 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 Service Mesh control plane using the cli

You can remove the Red Hat OpenShift Service Mesh control plane by using the cli. In this example, istio-system is the name of the control plane project.

Procedure

  1. Log in to the OpenShift Container Platform cli.

  2. Run the following command to delete the ServiceMeshMemberRoll resource.

    $ oc delete smmr -n istio-system default

  3. Run this command to retrieve the name of the installed ServiceMeshControlPlane:

    $ oc get smcp -n istio-system

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

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

Removing the installed Operators

You must remove the Operators to successfully remove Red Hat OpenShift Service Mesh. After you remove the Red Hat OpenShift Service Mesh Operator, you must remove the Kiali Operator, the Red Hat OpenShift distributed tracing platform Operator, and the OpenShift Elasticsearch Operator.

Removing the Operators

Follow this procedure to remove the Operators that make up Red Hat OpenShift Service Mesh. Repeat the steps for each of the following Operators.

  • Red Hat OpenShift Service Mesh

  • Kiali

  • Red Hat OpenShift distributed tracing platform

  • OpenShift Elasticsearch

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 each Operator. Then, click the Operator name.

  3. On the the Operator Details page, select Uninstall Operator from the Actions menu. Follow the prompts to uninstall each Operator.

Clean up Operator resources

You can manually remove resources left behind after removing the Red Hat OpenShift Service Mesh Operator using the OpenShift Container Platform web console.

Prerequisites

  • An account with cluster administration access. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin role.

  • 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 distributed tracing platform as a stand-alone service without service mesh, do not delete the Jaeger resources.

    The OpenShift Elasticsearch Operator is installed in openshift-operators-redhat by default. The other 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 mutatingwebhookconfiguration/openshift-operators.servicemesh-resources.maistra.io
    $ oc delete svc maistra-admission-controller -n openshift-operators
    $ oc -n openshift-operators delete ds -lmaistra-version
    $ 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 cm -n openshift-operators maistra-operator-cabundle
    $ oc delete cm -n openshift-operators istio-cni-config
    $ oc delete sa -n openshift-operators istio-cni