Uninstalling watsonx Orchestrate

An instance administrator and cluster administrator can work together to uninstall watsonx Orchestrate.

Who needs to complete this task?

Instance administrator To uninstall watsonx Orchestrate, you must be an instance administrator. An instance administrator has permission to manage software in the following projects:

The operators project for the instance: The operators for this instance of Cloud Pak for Data are installed in the operators project. In the uninstall commands, the ${PROJECT_CPD_INST_OPERATORS} environment variable refers to the operators project.
The operands project for the instance: The Cloud Pak for Data control plane and the services for this instance of Cloud Pak for Data are installed in the operands project. In the uninstall commands, the ${PROJECT_CPD_INST_OPERANDS} environment variable refers to the operands project.

When do you need to complete this task?

Complete this task if you want to remove watsonx Orchestrate from an instance of Cloud Pak for Data.

Repeat as needed If you are responsible for multiple instances of Cloud Pak for Data, you can repeat this task to remove other instances of watsonx Orchestrate on the cluster.

Information you need to complete this task

Review the following information before you uninstall watsonx Orchestrate:

Environment variables

The commands in this task use environment variables so that you can run the commands exactly as written.

If you don't have the script that defines the environment variables, see Setting up installation environment variables.
To use the environment variables from the script, you must source the environment variables before you run the commands in this task. For example, run:
```
source ./cpd_vars.sh
```

Procedure

Complete the following tasks to uninstall watsonx Orchestrate:

Deleting the service instance
Uninstalling the service
Uninstalling watsonx Assistant
Uninstalling IBM App Connect in containers

Deleting the service instance

Before you uninstall watsonx Orchestrate, you must delete the watsonx Orchestrate service instance to ensure that the instance releases any resources that it reserved.

Who needs to complete this task?: A user with the Manage service instances permission must complete this task.

When do you need to complete this task?: Complete this task before you uninstall watsonx Orchestrate.

From the Cloud Pak for Data web client:

Log in to the web client as a user with sufficient permissions to complete the task.
From the menu, select Services > Instances.
Filter the list to show the orchestrate type.
Delete the orchestrate instance.

Uninstalling the service

To uninstall watsonx Orchestrate:

Log the cpd-cli in to the Red Hat® OpenShift® Container Platform cluster:
```
${CPDM_OC_LOGIN}
```
Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.

Delete the custom resource for watsonx Orchestrate.

cpd-cli manage delete-cr \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_orchestrate \
--include_dependency=true

Wait for the cpd-cli to return the following message before you proceed to the next step:

[SUCCESS]... The delete-cr command ran successfully

Delete the OLM objects for watsonx Orchestrate:

cpd-cli manage delete-olm-artifacts \
--cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--components=watsonx_orchestrate,wxo_components,wxo_apicatalog,wxo_digital_employee

Wait for the cpd-cli to return the following message:

[SUCCESS]... The delete-olm-artifacts command ran successfully

Clean up the persistent volume claims created by the watsonx Orchestrate service:

oc delete $(oc get pvc -n ${PROJECT_CPD_INST_OPERANDS} -o name | grep "wo-") -n ${PROJECT_CPD_INST_OPERANDS}

Clean up the secrets created by the watsonx Orchestrate service:

Clean up the secrets in the operands project:

oc delete $(oc get secret -n ${PROJECT_CPD_INST_OPERANDS} -o name | grep "wo-") -n ${PROJECT_CPD_INST_OPERANDS}

Clean up the secrets in the operators project:

oc delete secret ${PROJECT_CPD_INST_OPERANDS}-mongodb-wo-mongo-ops-manager-admin-key -n ${PROJECT_CPD_INST_OPERATORS}

Clean up the MongDBUser that is created by the watsonx Orchestrate service:
```
oc delete MongoDBUser wo-mongo -n ${PROJECT_CPD_INST_OPERANDS}
```

Uninstalling watsonx Assistant

Follow the appropriate guidance for your environment:

If you are not using watsonx Assistant outside of watsonx Orchestrate, follow the guidance in Uninstalling watsonx Assistant.
If you are using watsonx Assistant outside of watsonx Orchestrate, decide whether you want to remove the watsonx Assistant service instances that are associated with watsonx Orchestrate.
The default names for the service instances are wxo-assistant-ab and wxo-assistant-de. However, the names might be different depending on the options that you specified when you ran the cpd-cli manage setup-wxo-assistant command.

For more information on removing watsonx Assistant service instances, see Deleting service instances in Uninstalling watsonx Assistant.

Uninstalling IBM App Connect in containers

After you uninstall watsonx Orchestrate, a cluster administrator can uninstall App Connect. For more information, see Uninstalling App Connect in the App Connect product documentation.

Tip: When you run the commands in the App Connect documentation, replace namespaceName with ${PROJECT_IBM_APP_CONNECT}.

You can skip the steps for removing the following resources:

App Connect Designer instances
Integration servers
Switch server

The preceding resources are not created by the cpd-cli manage setup-appconnect command.