Destroy the created resources🔗

If you have previously used the Cloud Pak Deployer to create assets, you can destroy the assets with the same command.

Prepare for destroy🔗

Prepare for destroy on existing OpenShift🔗

Set environment variables for existing OpenShift🔗

Optional: set environment variables for deployer config and status directories. If not specified, respectively $HOME/cpd-config and $HOME/cpd-status will be used.

export STATUS_DIR=$HOME/cpd-status
export CONFIG_DIR=$HOME/cpd-config

• STATUS_DIR: The directory where the Cloud Pak Deployer keeps all status information and log files. Please note that if you have chosen to use a File Vault, the directory specified must be the one you used when you created the environment
• CONFIG_DIR: Directory that holds the configuration. This must be the same directory you used when you created the environment

Prepare for destroy on IBM Cloud🔗

Set environment variables for IBM Cloud🔗

export IBM_CLOUD_API_KEY=your_api_key

Optional: set environment variables for deployer config and status directories. If not specified, respectively $HOME/cpd-config and $HOME/cpd-status will be used.

export STATUS_DIR=$HOME/cpd-status
export CONFIG_DIR=$HOME/cpd-config

• IBM_CLOUD_API_KEY: This is the API key you generated using your IBM Cloud account, this is a 40+ character string
• STATUS_DIR: The directory where the Cloud Pak Deployer keeps all status information and log files. Please note that if you have chosen to use a File Vault, the directory specified must be the one you used when you created the environment
• CONFIG_DIR: Directory that holds the configuration. This must be the same directory you used when you created the environment

Prepare for destroy on AWS🔗

Set environment variables for AWS🔗

We assume that the vault already holds the mandatory secrets for AWS Access Key, Secret Access Key and ROSA login token.

export STATUS_DIR=$HOME/cpd-status
export CONFIG_DIR=$HOME/cpd-config

• STATUS_DIR: The directory where the Cloud Pak Deployer keeps all status information and log files. Please note that if you have chosen to use a File Vault, the directory specified must be the one you used when you created the environment
• CONFIG_DIR: Directory that holds the configuration. This must be the same directory you used when you created the environment

Prepare for destroy on Azure🔗

Set environment variables for Azure🔗

We assume that the vault already holds the mandatory secrets for Azure - Service principal id and its password, tenant id and ARO login token.

export STATUS_DIR=$HOME/cpd-status
export CONFIG_DIR=$HOME/cpd-config

• STATUS_DIR: The directory where the Cloud Pak Deployer keeps all status information and log files. Please note that if you have chosen to use a File Vault, the directory specified must be the one you used when you created the environment
• CONFIG_DIR: Directory that holds the configuration. This must be the same directory you used when you created the environment

Set path and alias for the deployer🔗

source ./set-env.sh

Run the Cloud Pak Deployer from the command line to uninstall the software🔗

cp-deploy.sh env destroy --confirm-destroy

Please ensure you specify the same extra (dynamic) variables that you used when you ran the env apply command.

When running the command, the container will start as a daemon and the command will tail-follow the logs. You can press Ctrl-C at any time to interrupt the logging but the container will continue to run in the background.

You can return to view the logs as follows:

cp-deploy.sh env logs

If you need to interrupt the process, use CTRL-C to stop the logging output and then use:

cp-deploy.sh env kill

Run the Cloud Pak Deployer from the OpenShift console to uninstall the software🔗

If you have deployed on an existing OpenShift cluster using the console, you can uninstall the software from the cloud-pak-deployer-debug-xxxxx pod.

• In the OpenShift console, open Workloads in the left menu, then select Pods
• From the top, select the cloud-pak-deployer project from the drop-down
• Find the cloud-pak-deployer-debug-xxxxx pod and open it
• Select the Terminal tab to open a command line
• Run cp-deploy.sh env destroy --confirm-destroy from the command line

The above steps will delete Cloud Pak for Data and watsonx from the cluster, based on the configuration that is kept in cloud-pak-deployer configuration map.

Run a script from the OpenShift console to uninstall the software🔗

If you have deployed on an existing OpenShift cluster using the console, you can uninstall the software from the cloud-pak-deployer-debug-xxxxx pod.

• In the OpenShift console, open Workloads in the left menu, then select Pods
• From the top, select the cloud-pak-deployer project from the drop-down
• Find the cloud-pak-deployer-debug-xxxxx pod and open it
• Select the Terminal tab to open a command line
• Run the cd /cloud-pak-deployer/scripts/cp4d command
• Run the ./cp4d-delete-instance.sh <namespace> command

The above steps will delete Cloud Pak for Data and watsonx from the select namespace and will also delete the operators. After that it will also delete the license manager, knative eventing, IBM certificate manager and any obsolete CRDs from the cluster.