v1.9.1
v1.9.1
2022-08-17
Download
https://github.com/vmware-tanzu/velero/releases/tag/v1.9.1
Container Image
velero/velero:v1.9.1
Documentation
Upgrading
https://velero.io/docs/v1.9/upgrade-to-1.9/
All changes
- Fix bsl validation bug: the BSL is validated continually and doesn't respect the validation period configured (#5112, @ywk253100)
- Modify BackupStoreGetter to avoid BSL spec changes (#5134, @sseago)
- Delay CA file deletion in PVB controller. (#5150, @jxun)
- Skip registering "crd-remap-version" plugin when feature flag "EnableAPIGroupVersions" is set (#5173, @reasonerjt)
- Fix restic backups to multiple backup storage locations bug (#5175, @qiuming-best)
- Make CSI snapshot creation timeout configurable. (#5189, @jxun)
- Add annotation "pv.kubernetes.io/migrated-to" for CSI checking. (#5186, @jxun)
- Bump up base image and package version to fix CVEs. (#5202, @ywk253100)
Known issues:
Before Velero v1.9.1, if k8s cluster enables CSI migration for in-tree volume plugin, Restic integrated in Velero cannot handle CSI-migrated volume mount path correctly. CSI and CSI-migrated volumes are mounted at /<kubelet-pod-directory>/volumes/kubernetes.io~*/<volume-name>/mount.
The other volumes are mounted at directory /<kubelet-pod-directory>/volumes/kubernetes.io~*/<volume-name>. Although the backup contains CSI-migrated volume can completes successfully with Velero version older than v1.9.1, but it cannot be used to restore, due to Velero before v1.9.1 cannot handle CSI migrated volume correctly.
If user uses Velero no older than v1.9.1 to restore with the broken backup, backup data will be restore into /mount directory into new volume. If user uses Velero older than v1.9.1 version to restore with broken backup, data will be restore into the mount point’s parent directory, so the data is not accessible for mounting pod. Please install v1.9.1 Velero, and create a backup to make it work. (#5149, @blackpiglet)
