Uninstalling capabilities from the command line

To remove all the deployed capabilities, delete the namespace that you used to install.

Before you begin

If you need to back up your data, make sure that you take the necessary steps to reinstall the deployment. For example, make a copy of the custom resource (CR) that you used in the environment. Make copies of the security definitions that are used to protect the configuration data in the environment. Make copies of the persistent volumes (PV) and persistent volume claims (PVC) in the environment.

About this task

Important: To add or remove capabilities to an existing deployment, specifically to remove a platform component, see Updating deployments.

Procedure

To uninstall the operator, run the scripts/deleteOperator.sh script.
```
cd cert-kubernetes
./scripts/deleteOperator.sh -n <namespace>
```
For more information about downloading cert-kubernetes, see Preparing for an Enterprise deployment.
You can delete your custom resource deployments by deleting the CR YAML file or the CR instance. The name of the instance is taken from the value of the name parameter in the CR YAML file. To retrieve the names of the instances, run the get command.
```
oc get ICP4ACluster
```
To delete an instance, run the delete command.
```
oc delete ICP4ACluster <MY-INSTANCE>
```
Note:
- For more information about the databases used by FileNet® Content Manager, see Deleting a domain and Preparing an object store database or tablespace for reuse.
- If you plan to reinstall the Application Engine database, you must drop the database and database objects (buffer pool and table spaces) after you delete Application Engine.
Verify that all the pods that you created with the operator are stopped and deleted.

What to do next

After you uninstall, you might want to clean up certain files and secrets that you applied to the cluster for specific capabilities.

If you now plan to install another instance of the Cloud Pak on the same cluster, check if the IBM Automation Foundation dependencies like Namespaces, OperandRequests, and so on are properly deleted.

For more information about uninstalling Common Services and Automation Foundation, see Uninstalling foundational services and Troubleshooting foundational services.