Backup and migrate Kubernetes applications and their persistent volumes
https://github.com/vmware-tanzu/velero/releases/tag/v1.12.3-rc.1
velero/velero:v1.12.3-rc.1
https://velero.io/docs/v1.12/upgrade-to-1.12/
https://github.com/vmware-tanzu/velero/releases/tag/v1.12.2
velero/velero:v1.12.2
https://velero.io/docs/v1.12/upgrade-to-1.12/
https://github.com/vmware-tanzu/velero/releases/tag/v1.12.2-rc.2
velero/velero:v1.12.2-rc.2
https://velero.io/docs/v1.12/upgrade-to-1.12/
https://github.com/vmware-tanzu/velero/releases/tag/v1.12.2-rc.1
velero/velero:v1.12.2-rc.1
https://velero.io/docs/v1.12/upgrade-to-1.12/
https://github.com/vmware-tanzu/velero/releases/tag/v1.12.1
velero/velero:v1.12.1
https://velero.io/docs/v1.12/upgrade-to-1.12/
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.
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.
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.
linux/arm/v7
and linux/ppc64le
platforms of the Velero server are removed as the base image doesn't support themorLabelSelectors
for backup, restore commands (#6881, @nilesh-akhade)https://github.com/vmware-tanzu/velero/releases/tag/v1.12.1-rc.1
velero/velero:v1.12.1-rc.1
https://velero.io/docs/v1.12/upgrade-to-1.12/
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.
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.
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.
orLabelSelectors
for backup, restore commands (#6881, @nilesh-akhade)https://github.com/vmware-tanzu/velero/releases/tag/v1.12.0
velero/velero:v1.12.0
https://velero.io/docs/v1.12/upgrade-to-1.12/
CSI Snapshot Data Movement refers to back up CSI snapshot data from the volatile and limited production environment into durable, heterogeneous, and scalable backup storage in a consistent manner; and restore the data to volumes in the original or alternative environment.
CSI Snapshot Data Movement is useful in below scenarios:
CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design (Volume Snapshot Data Movement design). Additionally, guidance on how to use the feature can be found in the Volume Snapshot Data Movement doc(Volume Snapshot Data Movement doc).
In many use cases, customers often need to substitute specific values in Kubernetes resources during the restoration process like changing the namespace, changing the storage class, etc.
To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More design details can be found in Resource Modifiers design (Resource Modifiers design). For instructions on how to use the feature, please refer to Resource Modifiers doc(Resource Modifiers doc).
Prior to version 1.12, the Velero CSI plugin would choose the VolumeSnapshotClass in the cluster based on matching driver names and the presence of the "velero.io/csi-volumesnapshot-class" label. However, this approach proved inadequate for many user scenarios.
With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More design details can be found in Multiple VolumeSnapshotClasses design (Multiple VolumeSnapshotClasses design). For instructions on how to use the feature, please refer to Multiple VolumeSnapshotClasses doc (Multiple VolumeSnapshotClasses doc).
Before v1.12, the restore controller would only delete restore resources but wouldn’t delete restore data from the backup storage location when the command velero restore delete
was executed. The only chance Velero deletes restores data from the backup storage location is when the associated backup is deleted.
In this version, Velero introduces a finalizer that ensures the cleanup of all associated data for restores when running the command velero restore delete
.
To fix CVEs and keep pace with Golang, Velero made changes as follows:
uploader-type
for Velero installation had a default value of "restic". However, starting from this version, the default value has been changed to "kopia". This means that Velero will now use Kopia as the default path for file system backup.ReadyToUse
in operation uses the operation's timeout. The default value is 4 hours.restore
, dataupload
, and datadownload
in this version, directly deleting Velero namespace may get stuck indefinitely because the pods responsible for handling the finalizers might be deleted before the resources attached to the finalizers. To avoid this issue, please use the command velero uninstall
to delete all the Velero resources or ensure that you handle the finalizer appropriately before deleting the Velero namespace.IsPodRunning
is called. (#6232, @kaovilai)https://github.com/vmware-tanzu/velero/releases/tag/v1.12.0-rc.2
velero/velero:v1.12.0-rc.2
https://velero.io/docs/v1.12/upgrade-to-1.12/
CSI Snapshot Data Movement refers to back up CSI snapshot data from the volatile and limited production environment into durable, heterogeneous, and scalable backup storage in a consistent manner; and restore the data to volumes in the original or alternative environment.
CSI Snapshot Data Movement is useful in below scenarios:
CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design (Volume Snapshot Data Movement). More details can be found in the design.
In many use cases, customers often need to substitute specific values in Kubernetes resources during the restoration process like changing the namespace, changing the storage class, etc.
To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More details can be found in Volume Snapshot Resource Modifiers design (Resource Modifiers).
Prior to version 1.12, the Velero CSI plugin would choose the VolumeSnapshotClass in the cluster based on matching driver names and the presence of the "velero.io/csi-volumesnapshot-class" label. However, this approach proved inadequate for many user scenarios.
With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More details can be found in Multiple VolumeSnapshotClasses design (Multiple VolumeSnapshotClasses).
Before v1.12, the restore controller would only delete restore resources but wouldn’t delete restore data from the backup storage location when the command velero restore delete
was executed. The only chance Velero deletes restores data from the backup storage location is when the associated backup is deleted.
In this version, Velero introduces a finalizer that ensures the cleanup of all associated data for restores when running the command velero restore delete
.
To fix CVEs and keep pace with Golang, Velero made changes as follows:
uploader-type
for Velero installation had a default value of "restic". However, starting from this version, the default value has been changed to "kopia". This means that Velero will now use Kopia as the default path for file system backup.ReadyToUse
in operation uses the operation's timeout. The default value is 4 hours.restore
, dataupload
, and datadownload
in this version, directly deleting Velero namespace may get stuck indefinitely because the pods responsible for handling the finalizers might be deleted before the resources attached to the finalizers. To avoid this issue, please use the command velero uninstall
to delete all the Velero resources or ensure that you handle the finalizer appropriately before deleting the Velero namespace.IsPodRunning
is called. (#6232, @kaovilai)https://github.com/vmware-tanzu/velero/releases/tag/v1.12.0-rc.1
velero/velero:v1.12.0-rc.1
https://velero.io/docs/v1.12/upgrade-to-1.12/
CSI Snapshot Data Movement refers to back up CSI snapshot data from the volatile and limited production environment into durable, heterogeneous, and scalable backup storage in a consistent manner; and restore the data to volumes in the original or alternative environment.
CSI Snapshot Data Movement is useful in below scenarios:
CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design (Volume Snapshot Data Movement). More details can be found in the design.
In many use cases, customers often need to substitute specific values in Kubernetes resources during the restoration process like changing the namespace, changing the storage class, etc.
To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More details can be found in Volume Snapshot Resource Modifiers design (Resource Modifiers).
Prior to version 1.12, the Velero CSI plugin would choose the VolumeSnapshotClass in the cluster based on matching driver names and the presence of the "velero.io/csi-volumesnapshot-class" label. However, this approach proved inadequate for many user scenarios.
With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More details can be found in Multiple VolumeSnapshotClasses design (Multiple VolumeSnapshotClasses).
Before v1.12, the restore controller would only delete restore resources but wouldn’t delete restore data from the backup storage location when the command velero restore delete
was executed. The only chance Velero deletes restores data from the backup storage location is when the associated backup is deleted.
In this version, Velero introduces a finalizer that ensures the cleanup of all associated data for restores when running the command velero restore delete
.
To fix CVEs and keep pace with Golang, Velero made changes as follows:
uploader-type
for Velero installation had a default value of "restic". However, starting from this version, the default value has been changed to "kopia". This means that Velero will now use Kopia as the default path for file system backup.ReadyToUse
in operation uses the operation's timeout. The default value is 4 hours.IsPodRunning
is called. (#6232, @kaovilai)https://github.com/vmware-tanzu/velero/releases/tag/v1.11.1
velero/velero:v1.11.1
https://velero.io/docs/v1.11/upgrade-to-1.11/