velero version history

- Skip VGS cleanup when backup didn't use VolumeGroupSnapshots - Fix backup performance regression with includedNamespaces ["*"] - Fix DataUploadDeleteAction creating mislabeled ConfigMaps causing Kopia snapshot leaks

## v1.18.2-rc.2 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.2-rc.2 ### Container Image `velero/velero:v1.18.2-rc.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)

## v1.18.2 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.2-rc.1 ### Container Image `velero/velero:v1.18.2-rc.1` ### 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)

## v1.18.1 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.1 ### Container Image `velero/velero:v1.18.1` ### Documentation https://velero.io/docs/v1.18/ ### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ### All Changes * Fix wildcard expansion when includes is empty and excludes has wildcards (#9743, @Joeavaikath) * Backporting PR #9700 and #9693, fix issue #9699, add a 2-second gap between temporary CSI VolumeSnapshotContent create and delete operations. Enhance backup deletion logic to handle tarball download failures (#9731, @priyansh17) * Fix issue #9703, fix CSI PVC Backup Plugin list options to only list in installed namespace (#9708, @adam-jian-zhang) * Bump external-snapshotter to v8.4.0 and migrate VolumeGroupSnapshot API from v1beta1 to v1beta2 for Kubernetes 1.34+ compatibility (#9706, @shubham-pampattiwar) * Fix issue #9681, fix restores and podvolumerestores list options to only list in installed namespace (#9696, @adam-jian-zhang) * Fix issue #9659, in the case that PVB/PVR/DU/DD is cancelled before the data path is really started, call EndEvent to prevent data mover pod from crashing because of del

## v1.18.1 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.1-rc.2 ### Container Image `velero/velero:v1.18.1-rc.2` ### Documentation https://velero.io/docs/v1.18/ ### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ### All Changes * Fix wildcard expansion when includes is empty and excludes has wildcards (#9743, @Joeavaikath) * Backporting PR #9700 and #9693, fix issue #9699, add a 2-second gap between temporary CSI VolumeSnapshotContent create and delete operations. Enhance backup deletion logic to handle tarball download failures (#9731, @priyansh17) * Fix issue #9703, fix CSI PVC Backup Plugin list options to only list in installed namespace (#9708, @adam-jian-zhang) * Bump external-snapshotter to v8.4.0 and migrate VolumeGroupSnapshot API from v1beta1 to v1beta2 for Kubernetes 1.34+ compatibility (#9706, @shubham-pampattiwar) * Fix issue #9681, fix restores and podvolumerestores list options to only list in installed namespace (#9696, @adam-jian-zhang) * Fix issue #9659, in the case that PVB/PVR/DU/DD is cancelled before the data path is really started, call EndEvent to prevent data mover pod from crashing beca

## v1.18.1 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.1 ### Container Image `velero/velero:v1.18.1` ### Documentation https://velero.io/docs/v1.18/ ### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ### All Changes * Fix wildcard expansion when includes is empty and excludes has wildcards (#9743, @Joeavaikath) * Backporting PR #9700 and #9693, fix issue #9699, add a 2-second gap between temporary CSI VolumeSnapshotContent create and delete operations. Enhance backup deletion logic to handle tarball download failures (#9731, @priyansh17) * Fix issue #9703, fix CSI PVC Backup Plugin list options to only list in installed namespace (#9708, @adam-jian-zhang) * Bump external-snapshotter to v8.4.0 and migrate VolumeGroupSnapshot API from v1beta1 to v1beta2 for Kubernetes 1.34+ compatibility (#9706, @shubham-pampattiwar) * Fix issue #9681, fix restores and podvolumerestores list options to only list in installed namespace (#9696, @adam-jian-zhang) * Fix issue #9659, in the case that PVB/PVR/DU/DD is cancelled before the data path is really started, call EndEvent to prevent data mover pod from crashing because of del

## v1.18 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.0 ### Container Image `velero/velero:v1.18.0` ### Documentation https://velero.io/docs/v1.18/ ### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ### Highlights #### Concurrent backup In v1.18, Velero is capable to process multiple backups concurrently. This is a significant usability improvement, especially for multiple tenants or multiple users case, backups submitted from different users could run their backups simultaneously without interfering with each other. Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. #### Cache volume for data movers In v1.18, Velero allows users to configure cache volumes for data mover pods during restore for CSI snapshot data movement and fs-backup. This brings below benefits: - Solve the problem that data mover pods fail to when pod's ephemeral disk is limited - Solve the problem that multiple data mover pods fail to run concurrently in one node when the node's ephemeral disk is limited - Working together with backup repository's cache limit configu

## v1.18 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.0-rc.2 ### Container Image `velero/velero:v1.18.0-rc.2` ### Documentation https://velero.io/docs/v1.18/ ### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ### Highlights #### Concurrent backup In v1.18, Velero is capable to process multiple backups concurrently. This is a significant usability improvement, especially for multiple tenants or multiple users case, backups submitted from different users could run their backups simultaneously without interfering with each other. Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. #### Cache volume for data movers In v1.18, Velero allows users to configure cache volumes for data mover pods during restore for CSI snapshot data movement and fs-backup. This brings below benefits: - Solve the problem that data mover pods fail to when pod's ephemeral disk is limited - Solve the problem that multiple data mover pods fail to run concurrently in one node when the node's ephemeral disk is limited - Working together with backup repository's cache lim

## v1.18 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.18.0-rc.1 ### Container Image `velero/velero:v1.18.0-rc.1` ### Documentation https://velero.io/docs/v1.18/ ### Upgrading https://velero.io/docs/v1.18/upgrade-to-1.18/ ### Highlights #### Concurrent backup In v1.18, Velero is capable to process multiple backups concurrently. This is a significant usability improvement, especially for multiple tenants or multiple users case, backups submitted from different users could run their backups simultaneously without interfering with each other. Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. #### Cache volume for data movers In v1.18, Velero allows users to configure cache volumes for data mover pods during restore for CSI snapshot data movement and fs-backup. This brings below benefits: - Solve the problem that data mover pods fail to when pod's ephemeral disk is limited - Solve the problem that multiple data mover pods fail to run concurrently in one node when the node's ephemeral disk is limited - Working together with backup repository's cache lim

## v1.17.2 ### Download https://github.com/vmware-tanzu/velero/releases/tag/v1.17.2 ### Container Image `velero/velero:v1.17.2` ### Documentation https://velero.io/docs/v1.17/ ### Upgrading https://velero.io/docs/v1.17/upgrade-to-1.17/ ### All Changes * Track actual resource names for GenerateName in restore status (#9409, @shubham-pampattiwar) * Fix managed fields patch for resources using GenerateName (#9408, @shubham-pampattiwar) * don't copy securitycontext from first container if configmap found (#9394, @sseago) * Add Role, RoleBinding, ClusterRole, and ClusterRoleBinding in restore sequence. (#9479, @blackpiglet)