Uninstalling Kubera OnPrem

Graceful uninstallation of Kubera OnPrem setup can be carried out using below mentioned steps:

In case there are more than one clusters connected to Kubera OnPrem setup, it is recommended to disconnect all the connected clusters(except the self connected cluster) from the UI itself and then start the Kubera OnPrem cleanup process.

STEP 1:

To uninstall Kubera OnPrem cluster, execute the following command:

For helm version < 3.0.x

helm delete <release name> --purge

For helm version >= 3.0.x

helm uninstall <realease name> -n <namespace>  

To know the current helm version, execute:

helm version

and, for knowing the current release name, execute:

helm ls --namespace <namespace>

STEP 2:

Delete the PVC from custom namespace

NOTE: 1. Custom namespace: The namespace where Kubera OnPrem was installed.

The custom namespace consists of server components of Kubera. To view the PVCs, execute the following command:

kubectl get pvc -n <custom_namespace>

Output:

NAME                                               STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
cassandra-data-cassandra-0                         Bound    pvc-940b63b0-260d-11ea-9d0d-42010a80020f   50Gi       RWO            standard       16m
data-mysql-0                                       Bound    pvc-93c03d3a-260d-11ea-9d0d-42010a80020f   50Gi       RWO            standard       16m
elasticsearch-logging-od-elasticsearch-logging-0   Bound    pvc-94295656-260d-11ea-9d0d-42010a80020f   50Gi       RWO            standard       16m
grafana-claim                                      Bound    pvc-91d3aeb1-260d-11ea-9d0d-42010a80020f   50Gi       RWO            standard       16m
mayastore                                          Bound    pvc-91d496b4-260d-11ea-9d0d-42010a80020f   10Gi       RWO            standard       16m

All the PVCs displayed above have to be deleted. Ensure only the above PVCs are present in the namespace where Kubera OnPrem is installed. To delete, execute:

kubectl delete pvc -n <custom_namespace> --all

NOTE: 
1. In case there are other PVCs deployed, delete only the above mentioned PVCs.

kubectl delete pvc -n <custom_namespace> <pvc_name>

2. Ensure, these PVCs are not in use by any pods, if so, delete the pods.

STEP 3:

Delete the 'maya-system' namespace.

After deletion of the server components of Kubera in Step 2, we need to delete client-side components present on the cluster where Kubera OnPrem is installed. These components are by default deployed in maya-system namespace in the same cluster where Kubera gets installed.

To delete maya-system namespace, execute:

kubectl delete ns maya-system

NOTE:  In some cases, you might encounter an error like the one given below,

Error: uninstallation completed with x error(s)

This is encountered when the cleanup is not successful. In such cases, verify if any Kubera related components are still present (specifically PV and PVC). If so, you need to delete them manually.
In case you face any other issue feel free to reach out to our customer success team.