Uninstalling IBM Cloud Pak® for Watson AIOps AI Manager

These instructions can be used to uninstall an online or offline (airgap) deployment.

Use the following instructions to uninstall your IBM Cloud Pak® for Watson AIOps AI Manager deployment, and to clean up the resources that it created.

Run the uninstall script
(Optional) Delete the AI Manager catalog

Before you begin

The oc_cli must be installed on your OpenShift cluster, and you must be logged in with oc login.

1. Run the uninstall script

Download the uninstall and cleanup script from here Opens in a new tab .

You can configure the script to uninstall and clean up your AI Manager deployment. Details on how to configure the script are provided in the same location.

You can configure which components and resources that were created by the AI Manager deployment are removed by the script. Review the following, and configure the script to remove them only if you are sure that they are not used by other CloudPaks on your OpenShift cluster, and that you do not want to persist the data in them.

Persistent Volume Claims (PVCs)
shared components that are used by other Cloud Paks

Warning: Follow this step with caution if other IBM Cloud Paks® are installed on your OpenShift cluster that might be sharing components and resources with your AI Manager deployment.

2. (Optional) Delete the AI Manager catalog

Warning: AI Manager is part of the ibm-operator-catalog catalog. Do not delete this catalog if you are using other operators from it.

If you do not require the ibm-operator-catalog catalog, then remove it with one of the following methods:

Online deployments:

Option 1: Delete the AI Manager catalog with the OpenShift console
Option 2: Delete the AI Manager catalog with the OpenShift CLI

Air-gapped (offline) deployments:

If you have an air-gapped deployment that was upgraded from a version earlier than 3.5, then use option 3, otherwise use option 4.

Option 3: Delete the AI Manager catalog in an upgraded air-gapped deployment
Option 4: Delete the AI Manager catalog in an air-gapped deployment

Option 1: Delete the AI Manager catalog with the OpenShift console

In the OpenShift console, select Administration > Cluster Settings.
Select the Configuration tab, and then select OperatorHub from the Configuration Resource column.
Select the Sources tab.
Select the CatalogSource that you want to remove.
Select Delete CatalogSource from the Actions list.
Verify that the CatalogSource that you removed is not shown in Administration > Cluster Settings > Configuration > OperatorHub.

Option 2: Delete the AI Manager catalog with the OpenShift CLI

Run the following command for the catalog that you want to remove.
```
oc delete catalogsource -n openshift-marketplace <catalogsource>
```
Where <catalogsource> is the name of the CatalogSource that you want to delete.
Verify that the catalog that you removed is not returned by the following command:
```
oc get catalogsource -n openshift-marketplace
```

Option 3: Delete the AI Manager catalog in an upgraded air-gapped deployment

If you have an air-gapped deployment of Cloud Pak for Watson AIOps, then remove the catalog by using the uninstall-catalog case action.

Export the following environment variables.

The local Docker registry that you specify must be the registry in your air-gapped environment that you created when you installed Cloud Pak for Watson AIOps. For more information, see Set up local image registry.

export CASE_NAME=ibm-cp-waiops
export CASE_VERSION=1.4.1
export CASE_ARCHIVE=$CASE_NAME-$CASE_VERSION.tgz
export OFFLINEDIR=$HOME/offline
export CASE_LOCAL_PATH=$OFFLINEDIR/$CASE_ARCHIVE
export CASE_INVENTORY_SETUP=cpwaiopsSetup
export NAMESPACE=openshift-marketplace
export LOCAL_DOCKER_REGISTRY_HOST=<IP_or_FQDN_of_local_docker_registry.>
export LOCAL_DOCKER_REGISTRY_PORT=443
export LOCAL_DOCKER_REGISTRY=$LOCAL_DOCKER_REGISTRY_HOST:$LOCAL_DOCKER_REGISTRY_PORT

Run the uninstall-catalog CASE action.

cloudctl case launch \
  --case $CASE_LOCAL_PATH \
 --inventory $CASE_INVENTORY_SETUP \
 --action uninstall-catalog \
 --namespace $NAMESPACE\
 --args "--registry $LOCAL_DOCKER_REGISTRY \
 --inputDir $OFFLINEDIR"

Verify that the catalog that you removed is not returned by the following command:
```
oc get catalogsource -n <namespace>
```
Where <namespace> is your AI Manager project (namespace).

Option 4: Delete the AI Manager catalog in an air-gapped deployment

If you have an air-gapped deployment of Cloud Pak for Watson AIOps, then remove the catalog by using the uninstall-catalog case action.

Export the following environment variables.

export CASE_NAME=ibm-cp-waiops
export CASE_VERSION=1.4.1
export CASE_INVENTORY_SETUP=cpwaiopsSetup
export TARGET_REGISTRY_HOST=<IP_or_FQDN_of_target_registry>
export TARGET_REGISTRY_PORT=<port_number_of_target_registry>
export TARGET_REGISTRY=$TARGET_REGISTRY_HOST:$TARGET_REGISTRY_PORT

Run the uninstall-catalog CASE action.

oc ibm-pak launch $CASE_NAME   \
--version $CASE_VERSION \ 
--action uninstall-catalog \
--inventory $CASE_INVENTORY_SETUP \
--namespace openshift-marketplace \
--args "--registry $TARGET_REGISTRY --recursive \
--inputDir ~/.ibm-pak/data/cases/$CASE_NAME/$CASE_VERSION"

Verify that the catalog that you removed is not returned by the following command:
```
oc get catalogsource -n openshift-marketplace
```

Note: If you are using IBM Storage Fusion or IBM Spectrum Scale Container Native storage, and some IBM® Automation foundation components remain after you complete uninstallation, then see the troubleshooting guidance in the IBM Automation foundation documentation Opens in a new tab .