Velero Monitoring Integration

This page provides details on the Velero monitoring integration that is available in the UI.

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.

# Velero Monitoring Integration

Challenge

Velero, formerly known as Heptio Ark was one of the first solutions that was developed and offered as a backup solution in the Kubernetes market. Velero being an open-source solution and being the only solution available in the market back in the day, was adopted by users as they started evaluating Kubernetes and its ecosystem of products for their organizations. New users to the Kubernetes space also leverage Velero from time-to-time from an evaluation perspective or for running business operations within a small scope.

Velero being an open-source solution does not provide enterprise-grade support. Along with that, existing users and Trilio prospects have complained about Velero not supporting a management console for monitoring backups and restores, issues with the technology itself and various other reasons - big and small. As a result, customers adopt Trilio to eliminate issues that they are facing with Velero or to use an enterprise-grade solution as they mature with Kubernetes and move from running in evaluation mode to running in production mode. As customers adopt and migrate their data protection solution to Trilio, they desire a simple way to monitor and visualize their existing data protection landscape that they have with Velero.

Solution

As customers move from Velero to Trilio - having visibility into their existing Velero resources as well as new Trilio resource through a single pane of glass becomes a critical need. As a result, Trilio has developed the Velero integration feature which allows users to monitor Velero Backups, Velero Restores and Velero Backup Repositories from the Trilio for Kubernetes management console itself.

Trilio leverages appropriate Velero CRDs and parses information from the CRDs to populate and build the following views:

Backup - Based on Velero Backup CRD

Restore - Based on Velero Restore CRD

Targets - Based on BackupStorageLocation and VolumeSnapshotLocation CRDS

ISV Solutions leveraging Velero

Based on the Velero integration that Trilio has provided, ISVs that are leveraging Velero under the covers will also be supported via this integration. For example, OADP operator from Red Hat will automatically be picked by the Trilio controller and a list backups, restores and targets can be visualized through the Velero Integration feature provided.

Last updated