Velero (backup tool)

Velero (backup tool)
Name	Velero
Developer	VMware
Released	2017
Programming language	Go
Operating system	Linux
Platform	Kubernetes
Genre	Backup software
License	Apache License 2.0

Velero (backup tool) Velero is an open-source disaster recovery and data protection tool for Kubernetes clusters. It provides backup, restore, and migration capabilities to protect workloads running on Kubernetes and containerized platforms such as Docker and CRI-O. Developed initially by a team associated with Heptio and later maintained by VMware, Velero integrates with cloud providers including Amazon Web Services, Microsoft Azure, and Google Cloud Platform.

Overview

Velero emerged from efforts at Heptio to provide native backup for Kubernetes resources and persistent volumes, following operational challenges visible in projects like KubeCon discussions and reports from CNCF-hosted environments. The project became part of VMware after acquisition activity in the cloud-native ecosystem and has been referenced in presentations at KubeCon, OpenStack Summit, and workshops organized by Linux Foundation communities. Velero is implemented in Go (programming language) and is distributed under the Apache License terms, aligning with governance patterns seen in other projects like etcd and Prometheus.

Features

Velero offers scheduled backups of Kubernetes resources, point-in-time restores, and migration utilities for cluster portability used by operators in contexts similar to Kubernetes Federation experiments. It supports snapshotting of persistent volumes via cloud provider APIs such as Amazon EBS, Azure Disk Storage, and Google Compute Engine persistent disk, and can store backups in object stores like Amazon S3, Azure Blob Storage, and Google Cloud Storage. The tool includes declarative APIs that integrate with controllers similar to patterns in Helm and Operators and supports hooks and plugins comparable to extension models used by CNI plugins. Velero's feature set intersects with data protection principles documented by bodies like NIST and practices advocated in DevOps and Site Reliability Engineering events.

Architecture and components

Velero's architecture centers on a server-side controller and a client CLI, mirroring control-plane patterns found in Kubernetes itself and in projects such as kubectl and kubeadm. Core components include the Velero server deployment, a controller-manager, and a restic or CSI-based integrator for volume snapshots—paralleling snapshot approaches in Restic (software) and Container Storage Interface. Backups are stored as objects in cloud object storage, interoperating with services like Amazon S3, Azure Blob Storage, and Google Cloud Storage. The design uses Custom Resource Definitions similar to resources defined by Istio and Linkerd, and interacts with identity and access models implemented by AWS IAM, Azure Active Directory, and Google Cloud IAM for credentialed operations.

Installation and configuration

Installing Velero typically uses package and automation tools found in the cloud-native toolchain such as kubectl, Helm (software), and platform provisions from Terraform. Operators configure credentials for cloud providers using constructs managed by AWS IAM, Azure Service Principal, or Google Cloud Service Account, and create backup storage locations and volume snapshot locations through Velero CRDs configured via manifests consistent with Kubernetes API patterns. Deployment workflows often appear alongside infrastructure-as-code templates authored for Amazon EC2, Azure Virtual Machines, or Google Compute Engine instances, and are validated in CI contexts like Jenkins or GitHub Actions pipelines.

Usage and workflows

Common Velero workflows include scheduled backups, ad-hoc restores, and cluster migration sequences used in platform upgrades influenced by playbooks from Kubernetes SIGs and operator runbooks from SRE teams. Administrators use the Velero CLI to create Backup and Restore CRs, tag backups for retention policies analogous to policies in BC/DR frameworks, and test restores in staging clusters provisioned through Vagrant, Minikube, or Kind (Kubernetes IN Docker). Integration with snapshot providers enables consistent restores for stateful applications like PostgreSQL, MySQL, and MongoDB running on Kubernetes StatefulSet patterns.

Integrations and ecosystem

Velero integrates with cloud provider snapshot APIs (for example, Amazon EBS, Azure Disk Storage, Google Persistent Disk) and object stores compatible with S3 API implementations, including vendors like MinIO and managed services from DigitalOcean. The project supports plugin extensions written in Go (programming language) for new storage and snapshot providers, and interacts with workflow and CI systems including Argo CD, Flux (software), and Jenkins X. In the broader ecosystem, Velero complements monitoring stacks such as Prometheus and logging systems like ELK Stack when used in comprehensive platform resilience strategies.

Development, governance, and community

Velero development is hosted in public repositories and follows contribution workflows similar to those in Kubernetes and etcd projects, with issue tracking and pull request reviews performed on platforms tied to GitHub. Governance involves maintainers from VMware and community contributors spanning cloud vendors and service providers. The community coordinates via forums and events such as KubeCon, CloudNativeCon, and working groups within the Cloud Native Computing Foundation. Documentation, testing, and roadmap discussions reflect collaborative models used by projects like Prometheus and Helm.

Category:Backup software Category:Kubernetes Category:Open-source software