Update dependency vmware-tanzu/velero to v1.12.1

This MR contains the following updates:

Package	Type	Update	Change
vmware-tanzu/velero	ironbank-github	patch	v1.12.0 -> v1.12.1
vmware-tanzu/velero		patch	v1.12.0 -> v1.12.1

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the logs for more information.

---

Release Notes

vmware-tanzu/velero

v1.12.1

Compare Source

v1.12.1

2023-10-25

Download

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

Container Image

velero/velero:v1.12.1

Documentation

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

Upgrading

https://velero.io/docs/v1.12/upgrade-to-1.12/

Highlights

Data Mover Adds Support for Block Mode Volumes

For PersistentVolumes with volumeMode set as Block, the volumes are mounted as raw block devices in pods, in 1.12.1, Velero CSI snapshot data movement supports to backup and restore this kind of volumes under linux based Kubernetes clusters.

New Parameter in Installation to Enable Data Mover

The velero install sub-command now includes a new parameter,--default-snapshot-move-data, which configures Velero server to move data by default for all snapshots supporting data movement. This feature is useful for users who will always want to use VBDM for backups instead of plain CSI , as they no longer need to specify the --snapshot-move-data flag for each individual backup.

Velero Base Image change

The base image previously used by Velero was distroless, which contains several CVEs cannot be addressed quickly. As a result, Velero will now use paketobuildpacks image starting from this new version.

Limitations/Known issues

• The data mover's support for block mode volumes is currently only applicable to Linux environments.

Note

• The support for linux/arm/v7 and linux/ppc64le platforms of the Velero server are removed as the base image doesn't support them

All changes

• Import auth provider plugins (#​6970, @​0x113)
• Perf improvements for existing resource restore (#​6948, @​sseago)
• Retry failed create when using generateName (#​6943, @​sseago)
• Fix issue #​6647, add the --default-snapshot-move-data parameter to Velero install, so that users don't need to specify --snapshot-move-data per backup when they want to move snapshot data for all backups (#​6940, @​Lyndon-Li)
• Partially fix #​6734, guide Kubernetes' scheduler to spread backup pods evenly across nodes as much as possible, so that data mover backup could achieve better parallelism (#​6935, @​Lyndon-Li)
• Replace the base image with paketobuildpacks image (#​6934, @​ywk253100)
• Add support for block volumes with Kopia (#​6897, @​dzaninovic)
• Set ParallelUploadAboveSize as MaxInt64 and flush repo after setting up policy so that policy is retrieved correctly by TreeForSource (#​6886, @​Lyndon-Li)
• Kubernetes 1.27 new job label batch.kubernetes.io/controller-uid are deleted during restore per https://github.com/kubernetes/kubernetes/pull/114930 (#​6713, @​kaovilai)
• Add orLabelSelectors for backup, restore commands (#​6881, @​nilesh-akhade)
• Fix issue #​6859, move plugin depending podvolume functions to util pkg, so as to remove the dependencies to unnecessary repository packages like kopia, azure, etc. (#​6877, @​Lyndon-Li)
• Fix issue #​6786, always delete VSC regardless of the deletion policy (#​6873, @​Lyndon-Li)
• Fix #​6988, always get region from BSL if it is not empty (#​6991, @​Lyndon-Li)
• Limit PVC block mode logic to non-Windows platform. (#​6986, @​blackpiglet)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.