Velero Velero 1.18: Concurrent Backups, Cache Volumes, and More

We are pleased to announce the release of Velero v1.18. This release brings significant improvements in concurrency, performance, and observability, with contributions from engineers across multiple organizations.
Velero can now process multiple backups concurrently. This is a major usability improvement for multi-tenant environments – backups submitted by different users or teams run simultaneously without interfering with each other.
Previously, backups were serialized, meaning a long-running backup would block all other pending backups. With concurrent processing, backup throughput scales with available resources.
See the design document for details.
Velero 1.18 allows users to configure cache volumes for data mover pods during restore operations for both CSI snapshot data movement and fs-backup. This solves several real-world problems:
See the design document for details.
Users can now observe the incremental size of data mover backups for CSI snapshot data movement and fs-backup. This provides visibility into data reduction from incremental backups, helping teams understand and optimize their backup storage usage.
Velero now supports Glob regular expressions for namespace filters during backup and restore. This allows users to filter namespaces in batch – for example, backing up all namespaces matching team-* or excluding test-* namespaces.
VolumePolicy receives two improvements in this release:
Some backup repository operations are now executed outside the Velero server process, preventing OOM kills when working with large repositories.
VolumePolicy evaluation has been optimized for environments with large numbers of pods and PVCs, resulting in significantly improved performance through a PVC-to-Pod cache that avoids redundant lookups.
Events are now recorded in data mover pod diagnostics, giving users more information for troubleshooting when data mover pods fail.
Per the Velero deprecation policy, the PVC selected node feature is deprecated in v1.18. Velero now handles PVC selected-node annotations automatically, so no user action is required.
This release includes contributions from across the Velero community. Thank you to everyone who contributed:
To help you get started, see the documentation.
We are a Cloud Native Computing Foundation sandbox project.
Copyright Velero a Series of LF Projects, LLC.
For website terms of use, trademark policy and other project policies please see https://lfprojects.org/policies/.
This website does not use cookies or other tracking technology. This site is powered by Netlify.