# Velero v1.18.2 - Product: Velero (https://whatsnew.fyi/product/velero) - Vendor: VMware Tanzu - Date: 2026-06-26 - Version: v1.18.2 - Original notes: https://github.com/velero-io/velero/releases/tag/v1.18.2 - Permalink: https://whatsnew.fyi/product/velero/releases/v1.18.2 What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- - **fixed** — Skip VGS cleanup when backup did not use VolumeGroupSnapshots - **fixed** — Fix backup performance regression when using includedNamespaces ["*"] by restoring cross-namespace API listing optimization - **fixed** — Fix DataUploadDeleteAction creating snapshot-info ConfigMaps labeled with the wrong backup name when a DataUpload CR from another backup is incidentally captured in the backup tarball, which caused Kopia snapshots to be leaked in object storage on expiry of the real owning backup ##### v1.18.2 ###### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.2 ###### Container Image `velero/velero:v1.18.2` ###### Documentation https://velero.io/docs/v1.18/ ###### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ###### All Changes * Skip VGS cleanup when backup did not use VolumeGroupSnapshots (#9900, @shubham-pampattiwar) * Fix backup performance regression when using includedNamespaces ["*"] by restoring cross-namespace API listing optimization (#9870, @shubham-pampattiwar) * Fix DataUploadDeleteAction creating snapshot-info ConfigMaps labeled with the wrong backup name when a DataUpload CR from another backup is incidentally captured in the backup tarball, which caused Kopia snapshots to be leaked in object storage on expiry of the real owning backup. (#9842, @christian-schlichtherle)