LogoLogo
5.0.X
5.0.X
  • About Trilio for Kubernetes
    • Welcome to Trilio For Kubernetes
    • Version 5.0.X Release Highlights
    • Compatibility Matrix
    • Marketplace Support
    • Features
    • Use Cases
  • Getting Started
    • Getting Started with Trilio on Red Hat OpenShift (OCP)
    • Getting Started with Trilio for Upstream Kubernetes (K8S)
    • Getting Started with Trilio for AWS Elastic Kubernetes Service (EKS)
    • Getting Started with Trilio on Google Kubernetes Engine (GKE)
    • Getting Started with Trilio on VMware Tanzu Kubernetes Grid (TKG)
    • More Trilio Supported Kubernetes Distributions
      • General Installation Prerequisites
      • Rancher Deployments
      • Azure Cloud AKS
      • Digital Ocean Cloud
      • Mirantis Kubernetes Engine
      • IBM Cloud
    • Licensing
    • Using Trilio
      • Overview
      • Post-Install Configuration
      • Management Console
        • About the UI
        • Navigating the UI
          • UI Login
          • Cluster Management (Home)
          • Backup & Recovery
            • Namespaces
              • Namespaces - Actions
              • Namespaces - Bulk Actions
            • Applications
              • Applications - Actions
              • Applications - Bulk Actions
            • Virtual Machines
              • Virtual Machine -Actions
              • Virtual Machine - Bulk Actions
            • Backup Plans
              • Create Backup Plans
              • Backup Plans - Actions
            • Targets
              • Create New Target
              • Targets - Actions
            • Hooks
              • Create Hook
              • Hooks - Actions
            • Policies
              • Create Policies
              • Policies - Actions
          • Monitoring
          • Guided Tours
        • UI How-to Guides
          • Multi-Cluster Management
          • Creating Backups
            • Pause Schedule Backups and Snapshots
            • Cancel InProgress Backups
            • Cleanup Failed Backups
          • Restoring Backups & Snapshots
            • Cross-Cluster Restores
            • Namespace & application scoped
            • Cluster scoped
          • Disaster Recovery Plan
          • Continuous Restore
      • Command-Line Interface
        • YAML Examples
        • Trilio Helm Operator Values
    • Upgrade
    • Air-Gapped Installations
    • Uninstall
  • Reference Guides
    • T4K Pod/Job Capabilities
      • Resource Quotas
    • Trilio Operator API Specifications
    • Custom Resource Definition - Application
  • Advanced Configuration
    • AWS S3 Target Permissions
    • Management Console
      • KubeConfig Authenticaton
      • Authentication Methods Via Dex
      • UI Authentication
      • RBAC Authentication
      • Configuring the UI
    • Resource Request Requirements
      • Fine Tuning Resource Requests and Limits
    • Observability
      • Observability of Trilio with Prometheus and Grafana
      • Exported Prometheus Metrics
      • Observability of Trilio with Openshift Monitoring
      • T4K Integration with Observability Stack
    • Modifying Default T4K Configuration
  • T4K Concepts
    • Supported Application Types
    • Support for Helm Releases
    • Support for OpenShift Operators
    • T4K Components
    • Backup and Restore Details
      • Immutable Backups
      • Application Centric Backups
    • Retention Process
      • Retention Use Case
    • Continuous Restore
      • Architecture and Concepts
  • Performance
    • 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
    • AWS RDS snapshots using T4K hooks
    • Deploying Trilio For Kubernetes with Openshift ACM Policies
  • Krew Plugins
    • T4K QuickStart Plugin
    • Trilio for Kubernetes Preflight Checks Plugin
    • T4K Log Collector Plugin
    • T4K Cleanup Plugin
  • Support
    • Troubleshooting Guide
    • Known Issues and Workarounds
    • Contacting Support
  • Appendix
    • Ignored Resources
    • OpenSource Software Disclosure
    • CSI Drivers
      • Installing VolumeSnapshot CRDs
      • Install AWS EBS CSI Driver
    • T4K Product Quickview
    • OpenShift OperatorHub Custom CatalogSource
      • Custom CatalogSource in a restricted environment
    • 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 Machines running on OpenShift
    • T4K For Volumes with Generic Storage
    • T4K Best Practices
Powered by GitBook
On this page
  • Application Uninstallation
  • RedHat OpenShift User Interface
  • Upstream Kubernetes
  • Complete T4K Cleanup
  • Automated Cleanup
  • Manual Cleanup

Was this helpful?

  1. Getting Started

Uninstall

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

PreviousAir-Gapped InstallationsNextT4K Pod/Job Capabilities

Was this helpful?

There are two types of uninstallation of T4K:

  • Application uninstallation

  • Complete T4K cleanup

Application Uninstallation

Application uninstallation only deletes the T4K application and keeps all T4K custom resources. Users can follow these steps in case retaining the backups after application uninstallation is required. e.g. upgrade

RedHat OpenShift User Interface

  1. Delete the Trilio Manager CR from Trilio for Kubernetes operator using OpenShift user interface console

  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.

Upstream Kubernetes

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

2. Uninstall the Helm Operator

helm uninstall triliovault-operator --namespace <T4K-installation-namespace>

Complete T4K Cleanup

Note: Complete cleanup of T4K will remove all of T4K's custom resources - backup, restore, target etc along with the application itself. If users wish to only remove application while keeping the backups as is, follow the application uninstallation guide mentioned above.

To cleanup 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 cleanup T4K - automated (via a Trilio provided plugin) or manually removing all the items.

Automated Cleanup

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 Cleanup

Users can manually cleanup components of the Trilio solution using the steps mentioned below

RedHat OpenShift User Interface

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

  2. Delete the Trilio Manager CR from Trilio for Kubernetes operator using OpenShift user interface console

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

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

Upstream Kubernetes

Use the following steps to cleanup 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 $(kubectl get crds | grep trilio | awk '{print $1}')

automated-cleanup (via the T4K Cleanup Plugin)
manual-cleanup