2026.09.11
Velero: Open-Source Backup, Restore, and Migration for Kubernetes
Velero backs up and restores Kubernetes resources and persistent volumes, while also supporting cluster migration and environment replication. Teams should verify version compatibility and plan storage, permissions, and recovery testing before adoption.
What it is for
Velero is an open-source tool for backing up and restoring Kubernetes cluster resources and persistent volumes. Its documented use cases also include migrating resources to another cluster and replicating a production cluster to development or testing environments. The README states that Velero can run with a public cloud platform or on premises.
The project has two main parts: a server running in the Kubernetes cluster and a command-line client running locally. This model fits platform engineering, DevOps, and Kubernetes operations teams that want cluster-side execution with local administrative control.
Known capabilities and suitable users
Velero is relevant to organizations building Kubernetes disaster-recovery procedures, as well as teams that frequently create environments, migrate clusters, or maintain development and test copies. Its resource backup and restore model can also support operators managing multiple clusters, although the supplied sources do not quantify recovery performance.
The supplied release record identifies v1.18.2 as published on June 26, 2026. Its notes include fixes for skipping VolumeGroupSnapshots cleanup when snapshots were not used, a backup performance regression involving includedNamespaces: ["*"], and incorrect backup-name labels on snapshot-information ConfigMaps in a specific DataUpload scenario. These notes should not be treated as a general performance or security claim.
Limitations before adoption
Compatibility should be checked as a concrete version combination rather than assumed from Kubernetes support alone. The README’s matrix lists the expected Kubernetes compatibility for Velero 1.18 as 1.18-latest and records testing on Kubernetes 1.33.7, 1.34.1, and 1.35.0. It also states that maintainers cannot test every combination and recommends testing before installing or upgrading when using another Kubernetes version.
Before adoption, pin the Velero and Kubernetes versions, read the matching documentation and release notes, and validate backup, restore, and upgrade paths in an environment close to production. Teams should specifically review persistent-volume workflows, cluster permissions, backup storage, and retention policies. The supplied sources do not specify minimum hardware, a complete storage-backend list, recovery-time targets, or performance figures, so those details remain unconfirmed.
Deployment considerations
Plan the operational boundary between the in-cluster server and the locally used CLI. Ownership should be clear for backup policies, credentials, storage lifecycle, and restore approval. Public-cloud and on-premises operation are both within the project’s stated scope, but actual capabilities should be verified against the target version documentation and environment tests.
The repository metadata identifies Apache License 2.0 and shows that the repository is not archived. This provides useful licensing and maintenance-status information for teams seeking a self-managed open-source option, but it does not replace review of version support, dependencies, and internal compliance requirements.
Sources
Sources checked: 2026-09-11
For deployment help, see the straw-dog service shop and check the scope and server requirements before purchasing.