LogoLogo
2.0.X-2.10.X(Deprecated)
5.0.X4.0.X3.1.X3.0.X2.0.X-2.10.X(Deprecated)1.0.X-1.1.X(Deprecated)
2.0.X-2.10.X(Deprecated)
5.0.X4.0.X3.1.X3.0.X2.0.X-2.10.X(Deprecated)1.0.X-1.1.X(Deprecated)
  • Welcome to Trilio For Kubernetes (T4K)
  • Compatibility Matrix
  • Kubernetes Application Types
  • Features
  • Use Cases
  • Release Notes
  • Getting Started
    • Install Options
      • Quick Start
      • Standard Installation
        • Red Hat OpenShift
        • Upstream Kubernetes
        • Rancher Deployments
        • EKS/AKS/GKE
        • Digital Ocean Cloud
        • VMware Tanzu Kubernetes Grid (TKG)
        • Mirantis Kubernetes Engine
        • IBM Cloud
      • Upgrade
        • T4K 2.0.X to T4K 2.X Upgrade
        • Operator Upgrade 2.0.X to 2.X
    • Licensing
    • Management Console (UI)
    • Trilio APIs
    • Uninstall Options
  • Architecture
    • Architectural Components
    • Backup and Restore Details
    • Backup Retention Process
      • Retention Use Case
    • Permissions
      • T4K Pod/Job Capabilities
      • AWS S3 Target Permissions
    • Resource Requirements and Limits
    • APIs and Command Line Reference
      • Trilio Operator Helm Values
      • Custom Resource Definitions - Operator
        • Examples
      • Custom Resource Definition - Application
        • Examples
      • Target Browser API
  • Operation
    • Operate
    • Observability
  • Management Console UI
    • About the UI
    • UI Authentication
      • KubeConfig Authenticaton
      • Authentication Methods Via Dex
      • RBAC Authentication
    • Configuring the UI
    • Navigating the UI
      • UI Login
      • Cluster Management (Home)
      • Backup & Recovery
        • Namespaces
          • Namespaces - Actions
          • Namespaces - Bulk Actions
        • Applications
          • Applications - Actions
          • Applications - Bulk Actions
        • Backup Plans
          • Create Backup Plans
          • Backup Plans - Actions
        • Targets
          • Create New Target
          • Targets - Actions
      • Monitoring
        • Trilio Monitoring
        • Velero Monitoring Integration
      • Resource Management
      • Guided Tours
    • UI How-to Guides
      • Multi-Cluster Management
      • Creating Backups
      • Restoring Backups
        • Cross-Cluster Restores
      • Monitoring Details
      • Disaster Recovery Plan
      • Monitoring Velero with Trilio for Kubernetes
  • Performance
    • Modifying Default T4K Configuration
    • S3 as Backup Target
      • T4K S3 Fuse Plugin performance
    • Measuring Backup Performance
  • Ecosystem
    • T4K Integration with Slack using BotKube
    • Monitoring T4K Logs using ELK Stack
    • Rancher Navigation Links for Trilio Management Console
    • Optimize T4K Backups with StormForge
    • T4K GitHub Runner
    • Prometheus Metrics
    • AWS RDS snapshots using T4K hooks
  • Plugins
    • T4K QuickStart Plugin
    • T4K Preflight Checks Plugin
    • T4K Target Browser Plugin
    • T4K Log Collector Plugin
    • T4K Cleanup Plugin
    • OCP ETCD Plugin
    • RKE ETCD Plugin
  • Support
    • Troubleshooting Guide
      • Helm Support
      • Known Issues and Workarounds
    • Support
  • Appendix
    • Deploying Trilio For Kubernetes with Openshift ACM Policies
    • Ignored Resources
    • OpenSource Software Disclosure
    • CSI Drivers
      • Installing VolumeSnapshot CRDs
      • HostPath CSI Driver for T4K
    • T4K Product FAQ
    • OpenShift OperatorHub Custom CatalogSource
      • Custom CatalogSource in a restricted environment
    • Air-Gapped Install - Upstream Kubernetes
    • Marketplace Support
    • Configure OVH Object Storage as a Target
    • Connect T4K UI hosted with HTTPS to another cluster hosted with HTTP or vice versa
    • Fetch DigitalOcean Kubernetes Cluster kubeconfig for T4K UI Authentication
    • Force Update T4K Operator in Rancher Marketplace
    • Backup and Restore Virtual Machine running on OpenShift
    • T4K For Volumes with Generic Storage
    • T4K Resource Usage
Powered by GitBook
On this page
  • Uninstall Options
  • Automated Uninstall
  • Manual Uninstall
  1. Getting Started

Uninstall Options

This section describes how to uninstall Trilio for Kubernetes (T4K)

PreviousTrilio APIsNextArchitectural Components

Last updated 1 year ago

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)

  • Manual Uninstall

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

  1. Delete all the custom resources associated with Trilio - Backup, Restores, Targets, Hooks, BackupPlans, ClusterBackupPlan etc.

  2. 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.

  3. 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.

  1. Delete all the custom resources associated with Trilio - Backup, Restores, Targets, Hooks, BackupPlans, ClusterBackupPlan etc.

  2. Delete the Trilio Manager CR. When you uninstall the TVM CR, the triliovault-manager helm 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.