Uninstalling the operators and catalog sources

Remove the operators and catalog sources by using the OpenShift web console or the CLI.

This task must be performed by an OpenShift cluster administrator. For more information, see OpenShift roles and permissions.

Uninstalling using the OpenShift web console

Log into your OpenShift cluster.
In the navigation menu, click Operators > Installed Operators.
For Project, select the namespace where the Cloud Pak for Integration operators are installed.
Uninstall each operator by clicking the overflow menu (three-dot icon) icon for each operator and clicking Uninstall Operator.
Delete the CatalogSource for the operators. Only do this if you are not using other operators from the same catalog source.
1. Click Administration > Cluster Settings.
2. Click the Global Configuration tab, then click OperatorHub.
3. Select the Sources tab.
4. Delete the relevant catalog sources.

Uninstalling using the OpenShift CLI

Removing, or uninstalling with the OpenShift CLI requires the following steps:

Log into your OpenShift cluster, using your OpenShift user credentials:
```
oc login
```
Set the NAMESPACE environment variable to the namespace your instances are deployed in, for example:
```
export NAMESPACE=integration
```
Delete the Subscription for each operator in your namespace. If the operators were installed using the All namespaces on the cluster mode, these will be in the openshift-operators namespace. Otherwise, they will be in the namespace in which the operator was installed:
1. List the available entries in your namespace:
```
oc get subscription -n $NAMESPACE
```
2. Delete all Cloud Pak for Integration entries:
```
oc delete subscription -n $NAMESPACE <subscription-name>
```
Delete the ClusterServiceVersionfor each operator from the namespace. If the operators were installed using the All namespaces on the cluster mode, these will be in the openshift-operators namespace. Otherwise, they will be in the namespace in which the operator was installed:
1. List the available entries in your namespace:
```
oc get clusterserviceversions -n $NAMESPACE
```
2. Delete all Cloud Pak for Integration entries:
```
oc delete clusterserviceversions -n $NAMESPACE CSV1 CSV2 ... CSVn
```
Delete the Cloud Pak for Integration catalog sources.
1. List the available CatalogSource entries:
```
oc get catalogsource -n openshift-marketplace
```
2. Delete the Cloud Pak for Integration catalog sources:
```
oc delete catalogsource -n openshift-marketplace <catalog-source-name>
```

Removing the CustomResourceDefinitions

You can also remove the CustomResourceDefinitions (CRDs). CRDs are not removed when an operator is uninstalled. Removing the CRDs causes significant data loss across the entire OpenShift cluster (not just in a single namespace where a CRD may be installed). For this reason, remove the CRDs only if you want to remove Cloud Pak for Integration and all of its instances from the entire cluster.

Important: Removing the CRDs also deletes every instance of any deployed Cloud Pak for Integration component from the entire OpenShift cluster, not just from a single namespace.

To delete all Cloud Pak for Integration CRDs, run the following commands:

oc get crd -o name | grep apiconnect.ibm.com | xargs oc delete
oc get crd -o name | grep appconnect.ibm.com | xargs oc delete
oc get crd -o name | grep aspera.ibm.com | xargs oc delete
oc get crd -o name | grep cp4i.ibm.com | xargs oc delete
oc get crd -o name | grep datapower.ibm.com | xargs oc delete
oc get crd -o name | grep events.ibm.com | xargs oc delete
oc get crd -o name | grep eventstreams.ibm.com | xargs oc delete
oc get crd -o name | grep integration.ibm.com | xargs oc delete
oc get crd -o name | grep mq.ibm.com | xargs oc delete