Uninstalling manually

To remove all the deployed capabilities, delete the associated resources and the namespace that you used to install the deployment.

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

Uninstalling and cleaning up the cluster involves several separate high-level tasks.

Uninstalling the Content Cortex deployment.
Uninstalling the operators.
Deleting PVCs and PVs not containing data.
Deleting secrets.
Deleting the Content Cortex project or namespace.

To uninstall the Content Cortex deployment manually, use the following steps.

Procedure

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.
```
kubectl get FNCMCluster
```
To delete an instance, run the delete command.
```
kubectl delete FNCMCluster <MY-INSTANCE>
```

To uninstall the operator on run the following commands based on your platform.

For OCP:

export csvName=$(oc get subscription ibm-content-operator -o go-template --template '{{.status.installedCSV}}')

oc delete subscription ibm-content-operator 
oc delete clusterserviceversion "${csvName}"

For CNCF:

kubectl delete deploy ibm-content-operator
kubectl delete rolebinding ibm-content-operator
kubectl delete role ibm-content-operator
kubectl delete serviceaccount ibm-content-operator

Verify that all the pods that you created with the operator are stopped and deleted.

Note: Deleting the FNCMCluster and uninstalling the Content Cortex operator does not delete the existing PVs/PVC, or the databases that are used by the various components. Check the persisted data before you delete the PVs/PVCs manually to make sure you no longer want to keep them. Likewise, if the data no longer needs to be retained or reused you can delete the databases.

What to do next

If you plan to clean up the Content Cortex data, see the topic Cleaning up Content Cortex.