What velero-io/velero shipped
Written by FoxPlug from public releases; not affiliated with Velero. An automatic summary of the public release, pull request and commit data of github.com/velero-io/velero. Velero did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- Released v1.18.4-rc.1 with a fix for backup queue permanently stuck when a dequeued backup completes. Release
- Released v1.18.3 with a fix for duplicated InitContainer names generated in velero install CLI. Release
- Implemented namespace selection by label in resource policy, allowing dynamic include or exclude of namespaces from backups using Kubernetes label selectors. Pull request #10275
- Changed hashing algorithm to HMAC-SHA256-128 for kopia repository. Pull request #10579
- Fixed backup-finalizer to not set backup phase to Completed before PutBackupMetadata succeeds. Pull request #9646
- Fixed CVEs for v1.18.4 by bumping go.opentelemetry.io/otel/sdk to 1.45.0, google.golang.org/grpc to 1.83.2, and paketobuildpacks/run-jammy-tiny to 0.2.177. Pull request #10569
- Deduped entries in backuprequest.spec.excludeNamespaces when a namespace with velero.io/exclude-from-backup label is added. Pull request #10562
- Fixed schedule create command to properly accept and pass through --annotations flag instead of silently dropping it. Pull request #10549
- Added printer columns for BackupStorageLocation provider and access mode to kubectl output. Pull request #10441
- Added ability to customize the tolerations of maintenance jobs. Pull request #10553
Why it matters
v1.18.4-rc.1 and v1.18.3 releases address critical issues with backup queue handling and CLI installation. The namespace label selection feature in resource policies gives users more flexible backup filtering options. Multiple context propagation and CVE fixes improve reliability and security.
Changelog entry
- Fix backup queue permanently stuck when a dequeued backup completes Release
- Change hashing algorithm to HMAC-SHA256-128 for kopia repo Pull request #10579
- Fix backup-finalizer: do not set backup phase to Completed before PutBackupMetadata succeeds Pull request #9646
- Implement namespace selection by label in resource policy Pull request #10275
- Dedup entries in backuprequest.spec.excludeNamespaces Pull request #10562
- Fix schedule create dropping annotations Pull request #10549
- Fix CVEs for v1.18.4: bump go.opentelemetry.io/otel/sdk, google.golang.org/grpc, and paketobuildpacks/run-jammy-tiny Pull request #10569
- Customize the tolerations of maintenance job Pull request #10553
- Add printer columns for BackupStorageLocation provider and access mode Pull request #10441
- Propagate caller context in repository manager Forget/BatchForget Pull request #10554
Velero v1.18.3 and v1.18.4-rc.1 shipped this week with backup queue fixes, namespace label selection in resource policies, and CVE updates.
This week Velero released v1.18.3 and v1.18.4-rc.1, bringing important reliability and security improvements. Key additions include namespace selection by label in resource policies for more flexible backup filtering, fixes for backup queue handling, and CVE patches. The v1.18.4-rc.1 release candidate is now available for testing.
Week of September 14, 2026
What shipped
- Moved fallback full restore logic from PVC CSI RIA to data mover for better separation of concerns. Pull request #10541
- Added pre-flight check ensuring PVC is large enough to hold backed-up data during in-place restore. Pull request #10512
- Fixed in-place restore pre-flight check to identify volumes by CSI handle instead of PV name. Pull request #10530
- Fixed backup queue getting permanently stuck when a dequeued backup completes during the patch operation. Pull request #10521
- Added namespace mapping support for in-place restore with block data mover. Pull request #10461
- Fixed CSI PVC restore action to properly propagate context and standardize error handling. Pull request #10526
- Added support for skipped PVCs in VolumeInfos. Pull request #10525
- Fixed ServiceAccount token volume mount stripping to apply consistently across all container types during restore. Pull request #10349
- Added configurable tolerations for PodVolumeBackup and data mover pods via node-agent-configmap. Pull request #9575
- Fixed schedule reconciler to compare skipImmediately and lastSkipped by value instead of pointer. Pull request #10490
Why it matters
This week's changes address critical issues in in-place restore operations, backup queue management, and CSI volume handling that improve reliability and prevent data loss scenarios. Several fixes ensure proper context propagation, namespace mapping support, and preflight validation checks that operators depend on for safe restore operations.
Changelog entry
- Moved fallback full restore logic from PVC CSI RIA to data mover Pull request #10541
- Added in-place restore pre-flight check: PVC must be large enough for backed-up data Pull request #10512
- Fixed in-place restore pre-flight check to identify volumes by CSI volume handle Pull request #10530
- Fixed backup queue permanently stuck when dequeued backup completes during patch Pull request #10521
- Added namespace mapping support for in-place restore with block data mover Pull request #10461
- Fixed CSI PVC restore action to propagate context and standardize errors Pull request #10526
- Added support for skipped PVC in VolumeInfos Pull request #10525
- Fixed ServiceAccount token volume mount stripping for EphemeralContainers Pull request #10349
- Added configurable tolerations for PodVolumeBackup and data mover pods Pull request #9575
- Fixed schedule reconciler to compare skipImmediately and lastSkipped by value Pull request #10490
- Added nil checks to in-place restore preflight functions Pull request #10480
- Fixed snapshot-location get --selector flag to filter by label Pull request #10449
- Standardized error handling in CSI PVC restore action Pull request #10526
- Added documentation for block data mover Pull request #10537
- Documented --write-sparse-files flag for disk space issues during restore Pull request #9221
- Clarified --wait flag behavior in install command (default false) Pull request #10507
- Added test and documentation coverage for set-based label selectors on restore Pull request #10027
- Added fallback full flag to DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore CRs Pull request #10517
This week: in-place restore pre-flight checks, backup queue fixes, CSI volume handle identification, namespace mapping support, and better context propagation in restore operations.
This week's Velero updates focus on in-place restore reliability and data safety. Key improvements include preflight checks to ensure PVC capacity, fixes to identify volumes by CSI handle instead of PV name, prevention of backup queue deadlocks, namespace mapping support for block data movers, and better error handling in CSI restore operations. These changes strengthen restore workflows for production environments.