velero

v1.19

Download

https://github.com/velero-io/velero/releases/tag/v1.19.0

Container Image

velero/velero:v1.19.0

Documentation

https://velero.io/docs/v1.19/

Upgrading

https://velero.io/docs/v1.19/upgrade-to-1.19/

Highlights

Block data mover

Velero 1.19 introduces a block data mover (velero-block) for CSI snapshot data movement, enabling block-level backup and restore for both file system and block volumes backed by block storage. It integrates with the Kubernetes CSI Changed Block Tracking (CBT) API (https://kubernetes.io/blog/2025/09/25/csi-changed-block-tracking/) to transfer only changed blocks during incremental backups and restores with compatible CSI drivers, avoiding file system scanning overhead and improving backup and restore efficiency. For more information, check Velero document https://velero.io/docs/v1.19/csi-snapshot-data-movement/.

Volume data in-place restore

Velero 1.19 introduces volume data in-place restore, allowing backup data to be restored directly into existing volumes. It supports both full and incremental restores for CSI snapshot data movement (velero-fs and velero-block) and File System Backup, with incremental restores skipping unchanged data to reduce data transfer and recovery time. It also supports clone-and-restore workflows, where users first clone a volume from a snapshot and then perform an in-place restore into the cloned volume. For more information, check Velero document https://velero.io/docs/v1.19/volume-data-inplace-restore/.

Fine-grained filters

Velero 1.19 introduces fine-grained filters for backups and restores through ResourcePolicy ConfigMaps. Users can define per-namespace and per-resource-kind rules with independent label selectors and resource name patterns, providing more precise control over which namespaced and cluster-scoped resources are backed up or restored. For more information, check Velero document https://velero.io/docs/v1.19/fine-grained-backup-filters/ and https://velero.io/docs/v1.19/fine-grained-restore-filters/.

Namespace selection by labels

Velero 1.19 supports dynamically including or excluding namespaces from backups based on namespace labels through ResourcePolicy ConfigMaps. This simplifies backup and schedule management by automatically selecting matching namespaces when each backup starts, without maintaining explicit namespace lists. For more information, check Velero document https://velero.io/docs/v1.19/resource-filtering/#namespace-selection-by-label-backup-only.

Global volume policy

Velero 1.19 introduces global volume policies, allowing administrators to configure default volume backup rules for all backups through a shared ConfigMap. Backup-specific volume policies take precedence over global rules, providing consistent defaults while allowing customization for individual backups. For more information, check Velero document https://velero.io/docs/v1.19/resource-filtering/#global-backup-volume-policies.

Custom action type in volume policy

Velero 1.19 adds a custom action type to volume policies, allowing third-party BackupItemAction plugins to handle volume backups using custom methods. Users can select volumes for custom handling and pass plugin-specific parameters alongside existing snapshot and file system backup policies. For more information, check the Velero document https://velero.io/docs/v1.19/resource-filtering/#custom-volume-policy-actions.

Default restore resource modifier

Velero 1.19 allows administrators to configure a default restore resource modifier through a shared ConfigMap, automatically applying common resource transformations during restores. Individual restores can override the default with their own modifier or explicitly skip it, simplifying consistent restore customization. For more information, check the Velero document https://velero.io/docs/v1.19/restore-resource-modifiers/#default-resour

v1.18.4

Download

https://github.com/vmware-tanzu/velero/releases/tag/v1.18.4-rc.1

Container Image

velero/velero:v1.18.4-rc.1

Documentation

https://velero.io/docs/v1.18/

Upgrading

https://velero.io/docs/v1.18/upgrade-to-1.18/

All Changes

• Fix backup queue permanently stuck when a dequeued backup completes during the patch (#10539, @pujitha24)

v1.18.3

Download

https://github.com/vmware-tanzu/velero/releases/tag/v1.18.3

Container Image

velero/velero:v1.18.3

Documentation

https://velero.io/docs/v1.18/

Upgrading

https://velero.io/docs/v1.18/upgrade-to-1.18/

All Changes

• Avoid duplicated InitContainer names generated in velero install CLI. (#10396, @blackpiglet)
• Bound WaitRestoreExecHook polling with resourceTimeout to avoid an infinite wait when restore exec hooks never complete. (#10394, @nitishmalang)
• fix log format string mismatches that produce wrong or mangled output (#10392, @samay43)
• Skip DeleteSnapshot when ProviderSnapshotID is empty (#10381, @kaovilai)
• Fail backup validation when built-in data mover is requested but no node-agent pods are running (#10360, @Joeavaikath)
• Fix issue #10341, avoid mutating the cached node-agent LoadAffinity so the OS node selector term is not appended repeatedly to data mover pods (#10348, @shubham-pampattiwar)
• Fix PodVolumeBackup metadata loss on fs-backup timeout, which caused all fs-backup volumes to become unrestorable (#9999, @shubham-pampattiwar)
• Fix repo connection contest of the two repositories with the same storage type (#10377, @Lyndon-Li)
• Only sync finished backups from object storage (#10347, @chlins)
• Support copying namespace-scoped secrets and configmaps for backup and restore PVC provisioning to enable datamover backup/restore of encrypted CSI volumes (#10335, @shubham-pampattiwar)
• Remove PVC and PV inclusion check during creating PVR. (#10319, @blackpiglet)
• Fix a potential deadlock when resultsLock is held by the informer but blocked on resChan because the early quit of RestorePodVolumes (#10263, @Lyndon-Li)
• Fix restore-wait init container ignoring pod-level securityContext, falling back to hardcoded runAsUser 1000 instead of the workload's own uid/gid, causing fs-backup restores to deadlock at Init:0/1 on owner-restricted volumes (#10224, @kaovilai)
• Add use guide for restore fine-grained filters via resource policy (#10164, @adam-jian-zhang)
• Add restore.velero.io/must-include-additional-items so RestoreItemActions can opt in to bypassing global restore filters for AdditionalItems (mirrors the backup-side must-include annotation; no default behavior change for existing restores/plugins). Stop force-including VolumeSnapshotContents via resourceMustHave on every restore; CSI VolumeSnapshot/PVC RestoreItemActions now set restore.velero.io/must-include-additional-items so bound snapshot dependencies are restored only when their parent is restored (fixes #9957) (#10101, @adam-jian-zhang)
• User guide for backup fine-grained filters via resource policy, and add set based label selectors for fine-grained filters (#10072, @adam-jian-zhang)
• Fix issue #10032, prioritize exact namespace match in restore (#10052, @adam-jian-zhang)
• Fix issue #9997, cancel ongoing PVB on timeout and wait for all PVBs to terminal state (#10039, @Lyndon-Li)
• Add fine-grained filters for restore via resource policy, introduced resourcePolicy field for restoreSpec, which contains ClusterScopedFilterPolicy and NamespacedFilterPolicy section (#10015, @adam-jian-zhang)
• Add support for matching PVCs by volume mode and access mode in resource policies, and introduce the --global-backup-volume-policies-configmap server flag to merge cluster-wide backup volume policies into every backup. (#10012, @chlins)
• Add fine-grained filters for backup via resource policy, introduced ClusterScopedFilterPolicy and NamespacedFilterPolicy section for resource policy (#10011, @adam-jian-zhang)
• Add operation context to user-facing error messages in CR statuses and CLI output (#10474, @chlins)
• Fix issue 10454, enforce resource filter policies in memory in stage 1 to fix wildcard namespace bypassing issue (#10473, @adam-jian-zhang)

v1.18.3

Download

https://github.com/vmware-tanzu/velero/releases/tag/v1.18.3-rc.2

Container Image

velero/velero:v1.18.3-rc.2

Documentation

https://velero.io/docs/v1.18/

Upgrading

https://velero.io/docs/v1.18/upgrade-to-1.18/

All Changes

• Avoid duplicated InitContainer names generated in velero install CLI. (#10396, @blackpiglet)
• Bound WaitRestoreExecHook polling with resourceTimeout to avoid an infinite wait when restore exec hooks never complete. (#10394, @nitishmalang)
• fix log format string mismatches that produce wrong or mangled output (#10392, @samay43)
• Skip DeleteSnapshot when ProviderSnapshotID is empty (#10381, @kaovilai)
• Fail backup validation when built-in data mover is requested but no node-agent pods are running (#10360, @Joeavaikath)
• Fix issue #10341, avoid mutating the cached node-agent LoadAffinity so the OS node selector term is not appended repeatedly to data mover pods (#10348, @shubham-pampattiwar)
• Fix PodVolumeBackup metadata loss on fs-backup timeout, which caused all fs-backup volumes to become unrestorable (#9999, @shubham-pampattiwar)
• Fix repo connection contest of the two repositories with the same storage type (#10377, @Lyndon-Li)
• Only sync finished backups from object storage (#10347, @chlins)
• Support copying namespace-scoped secrets and configmaps for backup and restore PVC provisioning to enable datamover backup/restore of encrypted CSI volumes (#10335, @shubham-pampattiwar)
• Remove PVC and PV inclusion check during creating PVR. (#10319, @blackpiglet)
• Fix a potential deadlock when resultsLock is held by the informer but blocked on resChan because the early quit of RestorePodVolumes (#10263, @Lyndon-Li)
• Fix restore-wait init container ignoring pod-level securityContext, falling back to hardcoded runAsUser 1000 instead of the workload's own uid/gid, causing fs-backup restores to deadlock at Init:0/1 on owner-restricted volumes (#10224, @kaovilai)
• Add use guide for restore fine-grained filters via resource policy (#10164, @adam-jian-zhang)
• Add restore.velero.io/must-include-additional-items so RestoreItemActions can opt in to bypassing global restore filters for AdditionalItems (mirrors the backup-side must-include annotation; no default behavior change for existing restores/plugins). Stop force-including VolumeSnapshotContents via resourceMustHave on every restore; CSI VolumeSnapshot/PVC RestoreItemActions now set restore.velero.io/must-include-additional-items so bound snapshot dependencies are restored only when their parent is restored (fixes #9957) (#10101, @adam-jian-zhang)
• User guide for backup fine-grained filters via resource policy, and add set based label selectors for fine-grained filters (#10072, @adam-jian-zhang)
• Fix issue #10032, prioritize exact namespace match in restore (#10052, @adam-jian-zhang)
• Fix issue #9997, cancel ongoing PVB on timeout and wait for all PVBs to terminal state (#10039, @Lyndon-Li)
• Add fine-grained filters for restore via resource policy, introduced resourcePolicy field for restoreSpec, which contains ClusterScopedFilterPolicy and NamespacedFilterPolicy section (#10015, @adam-jian-zhang)
• Add support for matching PVCs by volume mode and access mode in resource policies, and introduce the --global-backup-volume-policies-configmap server flag to merge cluster-wide backup volume policies into every backup. (#10012, @chlins)
• Add fine-grained filters for backup via resource policy, introduced ClusterScopedFilterPolicy and NamespacedFilterPolicy section for resource policy (#10011, @adam-jian-zhang)
• Add operation context to user-facing error messages in CR statuses and CLI output (#10474, @chlins)
• Fix issue 10454, enforce resource filter policies in memory in stage 1 to fix wildcard namespace bypassing issue (#10473, @adam-jian-zhang)