Uninstall Options
This section describes how to uninstall Trilio for Kubernetes (T4K)
Deprecated Documentation
This document is deprecated and no longer supported. For accurate, up-to-date information, please refer to the documentation for the latest version of Trilio.
Uninstall Options
To uninstall Trilio for Kubernetes, the custom resources, CRDs and the Operator must be removed from the Kubernetes cluster or namespace. There are two ways users can uninstall T4K - automated (via a Trilio provided plugin) or manually removing all the items.
Automated Uninstall (via the T4K Cleanup Plugin)
Automated Uninstall
Trilio provides a plugin that automates the uninstall of all the resources and objects created to support the solution. The automation provides a non-interactive mode to allow unattended uninstall of the solution, and also provides an interactive mode to specifically uninstall different components. For further details, refer to the T4K Cleanup Plugin.
Manual Uninstall
Users can manually uninstall components of the Trilio solution. Since Trilio supports Operator Lifecycle Manager (OLM) and an upstream Helm-based operator, the steps required to uninstall Trilio for both types of Operators are different.
RedHat OpenShift User Interface
Delete all the custom resources associated with Trilio - Backup, Restores, Targets, Hooks, BackupPlans, ClusterBackupPlan etc.
Uninstall the Trilio for Kubernetes Operator - can be done directly from the OpenShift user interface console. After a successful uninstall the Trilio application will not be available.
Do not forget to delete the Trilio CRDs from the CRD page of OpenShift. Or run
oc delete crds $(oc get crds | grep trilio | awk '{print $1}')from OpenShift CLI
The application is now uninstalled and you can install a newer version.
Upstream Kubernetes
Please ensure all Trilio Custom Resources have been deleted from the environment before proceeding. This is required for a fresh new install of Trilio for Kubernetes
Use the following steps to uninstall Trilio for Kubernetes on all other certified Kubernetes distributions where the Trilio operator was installed via Helm.
Delete all the custom resources associated with Trilio - Backup, Restores, Targets, Hooks, BackupPlans, ClusterBackupPlan etc.
Delete the Trilio Manager CR. When you uninstall the TVM CR, the
triliovault-managerhelm release will be uninstalled.
kubectl delete tvm triliovault-manager --namespace <T4K-installation-namespace>
If delete TVM CR triliovault-manager gets stuck then on another terminal, edit the TVM CR, remove the finalizer section and save it.
kubectl edit tvm triliovault-manager --namespace <T4K-installation-namespace>
Remove below section:
finalizers:
- uninstall-helm-release
This will complete the delete operation.
3. Uninstall the Helm Operator
helm uninstall triliovault-operator --namespace <T4K-installation-namespace>
4. Delete all the Trilio CRDs
kubectl delete crds $(oc get crds | grep trilio | awk '{print $1}')
The application is now uninstalled and you can install a newer version.
Last updated
