NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #363 by repository stars
Latest stable
v1.3.2
Last release 4 days ago
18 Nov 2026
Ships unpredictably
gaps range from 8 days to 6.5 years
Most releases are documented
notes for 35 of 42 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
133 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Restic deprecation: ignore invalid PVB uploader for backup sync, backup delete and restore ( #10762 , @Lyndon-Li )
https://github.com/velero-io/velero/releases/tag/v1.19.0-rc.2
velero/velero:v1.19.0-rc.2
https://velero.io/docs/v1.19/upgrade-to-1.19/
Velero 1.19 introduces a block data mover (velero-block) for CSI snapshot data movement, enabling block-level backup and restore for both file system and block volumes backed by block storage. It integrates with the Kubernetes CSI Changed Block Tracking (CBT) API (https://kubernetes.io/blog/2025/09/25/csi-changed-block-tracking/) to transfer only changed blocks during incremental backups and restores with compatible CSI drivers, avoiding file system scanning overhead and improving backup and restore efficiency. For more information, check Velero document https://velero.io/docs/v1.19/csi-snapshot-data-movement/.
Velero 1.19 introduces volume data in-place restore, allowing backup data to be restored directly into existing volumes. It supports both full and incremental restores for CSI snapshot data movement (velero-fs and velero-block) and File System Backup, with incremental restores skipping unchanged data to reduce data transfer and recovery time. It also supports clone-and-restore workflows, where users first clone a volume from a snapshot and then perform an in-place restore into the cloned volume. For more information, check Velero document https://velero.io/docs/v1.19/volume-data-inplace-restore/.
Velero 1.19 introduces fine-grained filters for backups and restores through ResourcePolicy ConfigMaps. Users can define per-namespace and per-resource-kind rules with independent label selectors and resource name patterns, providing more precise control over which namespaced and cluster-scoped resources are backed up or restored. For more information, check Velero document https://velero.io/docs/v1.19/fine-grained-backup-filters/ and https://velero.io/docs/v1.19/fine-grained-restore-filters/.
Velero 1.19 supports dynamically including or excluding namespaces from backups based on namespace labels through ResourcePolicy ConfigMaps. This simplifies backup and schedule management by automatically selecting matching namespaces when each backup starts, without maintaining explicit namespace lists. For more information, check Velero document https://velero.io/docs/v1.19/resource-filtering/#namespace-selection-by-label-backup-only.
Velero 1.19 introduces global volume policies, allowing administrators to configure default volume backup rules for all backups through a shared ConfigMap. Backup-specific volume policies take precedence over global rules, providing consistent defaults while allowing customization for individual backups. For more information, check Velero document https://velero.io/docs/v1.19/resource-filtering/#global-backup-volume-policies.
Velero 1.19 adds a custom action type to volume policies, allowing third-party BackupItemAction plugins to handle volume backups using custom methods. Users can select volumes for custom handling and pass plugin-specific parameters alongside existing snapshot and file system backup policies. For more information, check the Velero document https://velero.io/docs/v1.19/resource-filtering/#custom-volume-policy-actions.
Velero 1.19 allows administrators to configure a default restore resource modifier through a shared ConfigMap, automatically applying common resource transformations during restores. Individual restores can override the default with their own modifier or explicitly skip it, simplifying consistent restore customization. For more information, check the Velero document https://velero.io/docs/v1.19/restore-resource-modifiers/#default-resource-modifiers.
Golang runtime: 1.27.3
kopia: 0.23.1
Block data mover incremental backups and restores support CSI drivers that can compute changed blocks without keeping the parent backup's snapshot; the CSI Changed Block Tracking KEP allows drivers either way.
Drivers that need the parent snapshot to still exist, for example Ceph RBD, are not supported in 1.19.0: their incremental backups read all allocated blocks instead of only the changed ones, and incremental restores run as full restores.
Support for these drivers is tracked in #10743.
CSI snapshot data movement restoring a pod that has both Immediate and WaitForFirstConsumer PVCs may stall, and the restore goes PartiallyFailed. If you are not running a multiple-zone cluster with storage topologies, you could work around this issue by setting the node-agent configuration restorePVC.ignoreDelayBinding: true; otherwise, you should avoid mounting both Immediate and WaitForFirstConsumer PVCs to a single pod.
Velero's code repository and Go module path changed from github.com/vmware-tanzu/velero to github.com/velero-io/velero. Downstream projects that import Velero as a library must update their imports and go.mod. Container images and CLI usage are unchanged.
Restic path for fs-backup is completely removed in 1.19. Therefore, Velero 1.19 marks restores from backups with Restic path as FailedValidation; backup sync ignores backups with Restic path, so they won't appear in the cluster even though they are kept as is in the backup storage; if there are existing backups with Restic path in the cluster, after upgrade to 1.19, deletion request of these backups will fail.
A default prepare queue length (5) is set for data movers, so that pending data mover pods won't occupy large amount of resources from the cluster. In the previous versions there is no limit. For more information about data mover prepare queue length, check Velero document https://velero.io/docs/v1.19/node-agent-prepare-queue-length/.
Kopia repository's hashing algorithm is changed from BLAKE2B-256-128 to HMAC-SHA256-128 for security compliance. This change applies to new repositories only, existing repositories still use BLAKE2B-256-128.
For security compliance, Velero 1.19 ignores user-provided spec.config.credentialsFile values in BackupStorageLocation (BSL) and VolumeSnapshotLocation (VSL). If you previously configured credentials this way, store them in a Kubernetes Secret in the Velero namespace and reference it using spec.credential.name and spec.credential.key.
Note truncated.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Restic deprecation: ignore invalid PVB uploader for backup sync, backup delete and restore ( #10762 , @Lyndon-Li )
https://github.com/velero-io/velero/releases/tag/v1.19.0
velero/velero:v1.19.0
https://velero.io/docs/v1.19/upgrade-to-1.19/
Velero 1.19 introduces a block data mover (velero-block) for CSI snapshot data movement, enabling block-level backup and restore for both file system and block volumes backed by block storage. It integrates with the Kubernetes CSI Changed Block Tracking (CBT) API (https://kubernetes.io/blog/2025/09/25/csi-changed-block-tracking/) to transfer only changed blocks during incremental backups and restores with compatible CSI drivers, avoiding file system scanning overhead and improving backup and restore efficiency. For more information, check Velero document https://velero.io/docs/v1.19/csi-snapshot-data-movement/.
Velero 1.19 introduces volume data in-place restore, allowing backup data to be restored directly into existing volumes. It supports both full and incremental restores for CSI snapshot data movement (velero-fs and velero-block) and File System Backup, with incremental restores skipping unchanged data to reduce data transfer and recovery time. It also supports clone-and-restore workflows, where users first clone a volume from a snapshot and then perform an in-place restore into the cloned volume. For more information, check Velero document https://velero.io/docs/v1.19/volume-data-inplace-restore/.
Velero 1.19 introduces fine-grained filters for backups and restores through ResourcePolicy ConfigMaps. Users can define per-namespace and per-resource-kind rules with independent label selectors and resource name patterns, providing more precise control over which namespaced and cluster-scoped resources are backed up or restored. For more information, check Velero document https://velero.io/docs/v1.19/fine-grained-backup-filters/ and https://velero.io/docs/v1.19/fine-grained-restore-filters/.
Velero 1.19 supports dynamically including or excluding namespaces from backups based on namespace labels through ResourcePolicy ConfigMaps. This simplifies backup and schedule management by automatically selecting matching namespaces when each backup starts, without maintaining explicit namespace lists. For more information, check Velero document https://velero.io/docs/v1.19/resource-filtering/#namespace-selection-by-label-backup-only.
Velero 1.19 introduces global volume policies, allowing administrators to configure default volume backup rules for all backups through a shared ConfigMap. Backup-specific volume policies take precedence over global rules, providing consistent defaults while allowing customization for individual backups. For more information, check Velero document https://velero.io/docs/v1.19/resource-filtering/#global-backup-volume-policies.
Velero 1.19 adds a custom action type to volume policies, allowing third-party BackupItemAction plugins to handle volume backups using custom methods. Users can select volumes for custom handling and pass plugin-specific parameters alongside existing snapshot and file system backup policies. For more information, check the Velero document https://velero.io/docs/v1.19/resource-filtering/#custom-volume-policy-actions.
Velero 1.19 allows administrators to configure a default restore resource modifier through a shared ConfigMap, automatically applying common resource transformations during restores. Individual restores can override the default with their own modifier or explicitly skip it, simplifying consistent restore customization. For more information, check the Velero document https://velero.io/docs/v1.19/restore-resource-modifiers/#default-resource-modifiers.
Golang runtime: 1.27.3
kopia: 0.23.1
Block data mover incremental backups and restores support CSI drivers that can compute changed blocks without keeping the parent backup's snapshot; the CSI Changed Block Tracking KEP allows drivers either way.
Drivers that need the parent snapshot to still exist, for example Ceph RBD, are not supported in 1.19.0: their incremental backups read all allocated blocks instead of only the changed ones, and incremental restores run as full restores.
Support for these drivers is tracked in #10743.
CSI snapshot data movement restoring a pod that has both Immediate and WaitForFirstConsumer PVCs may stall, and the restore goes PartiallyFailed. If you are not running a multiple-zone cluster with storage topologies, you could work around this issue by setting the node-agent configuration restorePVC.ignoreDelayBinding: true; otherwise, you should avoid mounting both Immediate and WaitForFirstConsumer PVCs to a single pod.
Velero's code repository and Go module path changed from github.com/vmware-tanzu/velero to github.com/velero-io/velero. Downstream projects that import Velero as a library must update their imports and go.mod. Container images and CLI usage are unchanged.
Restic path for fs-backup is completely removed in 1.19. Therefore, Velero 1.19 marks restores from backups with Restic path as FailedValidation; backup sync ignores backups with Restic path, so they won't appear in the cluster even though they are kept as is in the backup storage; if there are existing backups with Restic path in the cluster, after upgrade to 1.19, deletion request of these backups will fail.
A default prepare queue length (5) is set for data movers, so that pending data mover pods won't occupy large amount of resources from the cluster. In the previous versions there is no limit. For more information about data mover prepare queue length, check Velero document https://velero.io/docs/v1.19/node-agent-prepare-queue-length/.
Kopia repository's hashing algorithm is changed from BLAKE2B-256-128 to HMAC-SHA256-128 for security compliance. This change applies to new repositories only, existing repositories still use BLAKE2B-256-128.
For security compliance, Velero 1.19 ignores user-provided spec.config.credentialsFile values in BackupStorageLocation (BSL) and VolumeSnapshotLocation (VSL). If you previously configured credentials this way, store them in a Kubernetes Secret in the Velero namespace and reference it using spec.credential.name and spec.credential.key.
Note truncated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
https://velero.io/docs/v1.3.2/upgrade-to-1.3/
velero/velero:v1.3.2
https://velero.io/docs/v1.3.2/
https://velero.io/docs/v1.3.2/upgrade-to-1.3/
plugins/ as a valid top-level directory within backup storage locations. This directory is a place for plugin authors to store arbitrary data as needed. It is recommended to create an additional subdirectory under plugins/ specifically for your plugin, e.g. plugins/my-plugin-data/. (#2350, @skriss)velero restic repo get when last maintenance time is nil (#2315, @skriss)https://velero.io/docs/v1.3.1/upgrade-to-1.3/
velero/velero:v1.3.1
https://velero.io/docs/v1.3.1/
https://velero.io/docs/v1.3.1/upgrade-to-1.3/
Fixed a bug that caused failures when backing up CustomResourceDefinitions with whole numbers in numeric fields.
Replaced deprecated helm repo url at all it appearance at docs. (#2209, @markrity)
velero/velero:v1.3.0
https://velero.io/docs/v1.3.0/
https://velero.io/docs/v1.3.0/upgrade-to-1.3/
This release includes a number of related bug fixes and improvements to how Velero backs up and restores custom resource definitions (CRDs) and instances of those CRDs.
We found and fixed three issues around restoring CRDs that were originally created via the v1beta1 CRD API. The first issue affected CRDs that had the PreserveUnknownFields field set to true. These CRDs could not be restored into 1.16+ Kubernetes clusters, because the v1 CRD API does not allow this field to be set to true. We added code to the restore process to check for this scenario, to set the PreserveUnknownFields field to false, and to instead set x-kubernetes-preserve-unknown-fields to true in the OpenAPIv3 structural schema, per Kubernetes guidance. For more information on this, see the Kubernetes documentation. The second issue affected CRDs without structural schemas. These CRDs need to be backed up/restored through the v1beta1 API, since all CRDs created through the v1 API must have structural schemas. We added code to detect these CRDs and always back them up/restore them through the v1beta1 API. Finally, related to the previous issue, we found that our restore code was unable to handle backups with multiple API versions for a given resource type, and we’ve remediated this as well.
We also improved the CRD restore process to enable users to properly restore CRDs and instances of those CRDs in a single restore operation. Previously, users found that they needed to run two separate restores: one to restore the CRD(s), and another to restore instances of the CRD(s). This was due to two deficiencies in the Velero code. First, Velero did not wait for a CRD to be fully accepted by the Kubernetes API server and ready for serving before moving on; and second, Velero did not refresh its cached list of available APIs in the target cluster after restoring CRDs, so it was not aware that it could restore instances of those CRDs.
We fixed both of these issues by (1) adding code to wait for CRDs to be “ready” after restore before moving on, and (2) refreshing the cached list of APIs after restoring CRDs, so any instances of newly-restored CRDs could subsequently be restored.
With all of these fixes and improvements in place, we hope that the CRD backup and restore experience is now seamless across all supported versions of Kubernetes.
Thanks to community members @Prajyot-Parab and @shaneutt, Velero now provides multi-arch container images by using Docker manifest lists. We are currently publishing images for linux/amd64, linux/arm64, linux/arm, and linux/ppc64le in our Docker repository.
Users don’t need to change anything other than updating their version tag - the v1.3 image is velero/velero:v1.3.0, and Docker will automatically pull the proper architecture for the host.
For more information on manifest lists, see Docker’s documentation.
We fixed a large number of bugs and made some smaller usability improvements in this release. Here are a few highlights:
v1beta1 version (#2230, @skriss)replicasets.apps, not replicasets.extensions (#2157, @skriss)replicasets.apps and replicasets.extensions before deployments (#2120, @skriss)AWS_PROFILE) if multiple s3-compatible backupLocations are present (#2096, @dinesh)fsfreeze-pause image being published from this repo; replace it with ubuntu:bionic in the nginx example app (#2068, @skriss)--kubeconfig, $KUBECONFIG, or in-cluster config (#2057, @skriss)Replaced deprecated helm repo url at all it appearance at docs. (#2209, @markrity)
https://github.com/vmware-tanzu/velero/releases/tag/v1.3.0-beta.2
velero/velero:v1.3.0-beta.2
https://velero.io/docs/v1.3.0-beta.2/
kubectl set image \
--namespace velero \
deployment/velero velero=velero/velero:v1.3.0-beta.2
# if using restic:
kubectl set image \
--namespace velero \
daemonset/restic restic=velero/velero:v1.3.0-beta.2
See https://github.com/vmware-tanzu/velero/releases/tag/v1.3.0-beta.1 for additional changes since v1.2.0.
https://velero.io/docs/v1.3.0-beta.1/
velero/velero:v1.3.0-beta.1
https://velero.io/docs/v1.3.0-beta.1/
kubectl set image \
--namespace velero \
deployment/velero velero=velero/velero:v1.3.0-beta.1
# if using restic:
kubectl set image \
--namespace velero \
daemonset/restic restic=velero/velero:v1.3.0-beta.1
arm and arm64 images (#2227, @shaneutt)v1beta1 version (#2230, @skriss)ppc64le images and manifest lists (#1768, @prajyot)replicasets.apps, not replicasets.extensions (#2157, @skriss)replicasets.apps and replicasets.extensions before deployments (#2120, @skriss)AWS_PROFILE) if multiple s3-compatible backupLocations are present (#2096, @dinesh)fsfreeze-pause image being published from this repo; replace it with ubuntu:bionic in the nginx example app (#2068, @skriss)--kubeconfig, $KUBECONFIG, or in-cluster config (#2057, @skriss)Nothing published for this version
Nothing published for this version
Nothing published for this version
https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0
https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0
velero/velero:v1.2.0
Please note that as of this release we are no longer publishing new container images to gcr.io/heptio-images. The existing ones will remain there for the foreseeable future.
https://velero.io/docs/v1.2.0/
https://velero.io/docs/v1.2.0/upgrade-to-1.2/
Velero has had built-in support for AWS, Microsoft Azure, and Google Cloud Platform (GCP) since day 1. When Velero moved to a plugin architecture for object store providers and volume snapshotters in version 0.6, the code for these three providers was converted to use the plugin interface provided by this new architecture, but the cloud provider code still remained inside the Velero codebase. This put the AWS, Azure, and GCP plugins in a different position compared with other providers’ plugins, since they automatically shipped with the Velero binary and could include documentation in-tree.
With version 1.2, we’ve extracted the AWS, Azure, and GCP plugins into their own repositories, one per provider. We now also publish one plugin image per provider. This change brings these providers to parity with other providers’ plugin implementations, reduces the size of the core Velero binary by not requiring each provider’s SDK to be included, and opens the door for the plugins to be maintained and released independently of core Velero.
We’ve continued to work on improving Velero’s restic integration. With this release, we’ve made the following enhancements:
velero backup/restore describe --details command. The details are updated every 10 seconds. This provides a new level of visibility into restic operations for users.Before version 1.2, you could clone a Kubernetes namespace by backing it up and then restoring it to a different namespace in the same cluster by using the --namespace-mappings flag with the velero restore create command. However, in this scenario, Velero was unable to clone persistent volumes used by the namespace, leading to errors for users.
In version 1.2, Velero automatically detects when you are trying to clone an existing namespace, and clones the persistent volumes used by the namespace as well. This doesn’t require the user to specify any additional flags for the velero restore create command. This change lets you fully achieve your goal of cloning namespaces using persistent storage within a cluster.
To help you secure your important backup data, we’ve added support for more forms of server-side encryption of backup data on both AWS and GCP. Specifically:
serverSideEncryption: AES256 in a backup storage location’s config.kmsKeyName: <key name> in a backup storage location’s config.In Kubernetes 1.16, custom resource definitions (CRDs) reached general availability. Structural schemas are required for CRDs created in the apiextensions.k8s.io/v1 API group. Velero now defines a structural schema for each of its CRDs and automatically applies it the user runs the velero install command. The structural schemas enable the user to get quicker feedback when their backup, restore, or schedule request is invalid, so they can immediately remediate their request.
--allow-partially-failed flag to velero restore create for use with --from-schedule to allow partially-failed backups to be restored (#1994, @skriss)--no-default-backup-location flag to velero install (#1931, @Frank51)--plugins flag for velero install command. --plugins takes a list of container images to add as initcontainers. (#1930, @nrb)insecureSkipTLSVerify server config for AWS storage and --insecure-skip-tls-verify flag on client for self-signed certs (#1793, @s12chung)LD_LIBRARY_PATH (=/plugins) to the env variables of velero deployment. (#1893, @lintongj)metadata/revision file, do a full diff of bucket contents vs. cluster contents each sync interval (#1892, @skriss)serverSideEncryption config field in BackupStorageLocation (#1869, @skriss)restic prune interval to 7 days, add velero server/install flags for specifying an alternate default value. (#1864, @skriss)--use-restic and --wait are specified, wait up to a minute for restic daemonset to be ready (#1859, @skriss)--features argument to all velero commands to provide feature flags that can control enablement of pre-release features. (#1798, @nrb)--parent flag to prevent full volume rescans after pod reschedules (#1807, @skriss)velero restore create --namespace-mappings ... to create a second copy of a namespace in a cluster, create copies of the PVs used (#1779, @skriss)velero create backup command to create a Backup from an existing Schedule (#1734, @prydonius)https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0-beta.1
velero/velero:v1.2.0-beta.1
https://velero.io/docs/v1.2.0-beta.1/
If you're upgrading from a previous version of Velero, there are several changes you'll need to be aware of:
velero/velero:v1.2.0-beta.1.velero plugin add velero/velero-plugin-for-aws:v1.0.0-beta.1velero plugin add velero/velero-plugin-for-microsoft-azure:v1.0.0-beta.1velero plugin add velero/velero-plugin-for-gcp:v1.0.0-beta.1velero/velero:v1.2.0-beta.1.PodVolumeBackup and PodVolumeRestore custom resources and viewable via velero backup/restore describe while operations are in progress.velero install to enable validation of API fields.--namespace-mappings flag to clone a namespace within a cluster, PVs will now be cloned as needed.--no-default-backup-location flag to velero install (#1931, @Frank51)--plugins flag for velero install command. --plugins takes a list of container images to add as initcontainers. (#1930, @nrb)insecureSkipTLSVerify server config for AWS storage and --insecure-skip-tls-verify flag on client for self-signed certs (#1793, @s12chung)LD_LIBRARY_PATH (=/plugins) to the env variables of velero deployment. (#1893, @lintongj)metadata/revision file, do a full diff of bucket contents vs. cluster contents each sync interval (#1892, @skriss)serverSideEncryption config field in BackupStorageLocation (#1869, @skriss)restic prune interval to 7 days, add velero server/install flags for specifying an alternate default value. (#1864, @skriss)--use-restic and --wait are specified, wait up to a minute for restic daemonset to be ready (#1859, @skriss)--features argument to all velero commands to provide feature flags that can control enablement of pre-release features. (#1798, @nrb)--parent flag to prevent full volume rescans after pod reschedules (#1807, @skriss)velero restore create --namespace-mappings ... to create a second copy of a namespace in a cluster, create copies of the PVs used (#1779, @skriss)velero create backup command to create a Backup from an existing Schedule (#1734, @prydonius)--allow-partially-failed flag to velero restore create for use with --from-schedule to allow partially-failed backups to be restored (#1994, @skriss)https://github.com/heptio/velero/releases/tag/v1.1.0
gcr.io/heptio-images/velero:v1.1.0
https://velero.io/docs/v1.1.0/
If you are running Velero in a non-default namespace, i.e. any namespace other than velero, manual intervention is required when upgrading to v1.1. See upgrading to v1.1 for details.
A big focus of our work this cycle was continuing to improve support for restic. To that end, we’ve fixed the following bugs:
Along with our bug fixes, we’ve provided an easier way to move restic backups between storage providers. Different providers often have different StorageClasses, requiring user intervention to make restores successfully complete.
To make cross-provider moves simpler, we’ve introduced a StorageClass remapping plug-in. It allows you to automatically translate one StorageClass on PersistentVolumeClaims and PersistentVolumes to another. You can read more about it in our documentation.
We’ve also made several other enhancements to Velero that should benefit all users.
Users sometimes ask about recommendations for Velero’s resource allocation within their cluster. To help with this concern, we’ve added default resource requirements to the Velero Deployment and restic init containers, along with configurable requests and limits for the restic DaemonSet. All these values can be adjusted if your environment requires it.
We’ve also taken some time to improve Velero for the future by updating the Deployment and DaemonSet to use the apps/v1 API group, which will be the default in Kubernetes 1.16. This change means that velero install and the velero plugin commands will require Kubernetes 1.9 or later to work. Existing Velero installs will continue to work without needing changes, however.
In order to help you better understand what resources have been backed up, we’ve added a list of resources in the velero backup describe --details command. This change makes it easier to inspect a backup without having to download and extract it.
In the same vein, we’ve added the ability to put custom tags on cloud-provider snapshots. This approach should provide a better way to keep track of the resources being created in your cloud account. To add a label to a snapshot at backup time, use the --labels argument in the velero backup create command.
Our final change for increasing visibility into your Velero installation is the velero plugin get command. This command will report all the plug-ins within the Velero deployment..
Velero has previously used a restore-only flag on the server to control whether a cluster could write backups to object storage. With Velero 1.1, we’ve now moved the restore-only behavior into read-only BackupStorageLocations. This move means that the Velero server can use a BackupStorageLocation as a source to restore from, but not for backups, while still retaining the ability to back up to other configured locations. In the future, the --restore-only flag will be removed in favor of configuring read-only BackupStorageLocations.
We appreciate all community contributions, whether they be pull requests, bug reports, feature requests, or just questions. With this release, we wanted to draw attention to a few contributions in particular:
For users of node-based IAM authentication systems such as kube2iam, velero install now supports the --pod-annotations argument for applying necessary annotations at install time. This support should make velero install more flexible for scenarios that do not use Secrets for access to their cloud buckets and volumes. You can read more about how to use this new argument in our AWS documentation. Huge thanks to Traci Kamp for this contribution.
Structured logging is important for any application, and Velero is no different. Starting with version 1.1, the Velero server can now output its logs in a JSON format, allowing easier parsing and ingestion. Thank you to Donovan Carthew for this feature.
AWS supports multiple profiles for accessing object storage, but in the past Velero only used the default. With v.1.1, you can set the profile key on yourBackupStorageLocation to specify an alternate profile. If no profile is set, the default one is used, making this change backward compatible. Thanks Pranav Gaikwad for this change.
Finally, thanks to testing by Dylan Murray and Scott Seago, an issue with running Velero in non-default namespaces was found in our beta version for this release. If you’re running Velero in a namespace other than velero, please follow the upgrade instructions.
VELERO_NAMESPACE to determine what namespace Velero server is running in. For any v1.0 installations using a different namespace, the VELERO_NAMESPACE environment variable will need to be set to the correct namespace. (#1748, @nrb)velero backup describe --details (#1741, @prydonius)--secret-file flag on velero install optional, add --no-secret flag for explicit confirmation (#1699, @nrb)velero install and velero plugin add/remove commands will now require Kubernetes 1.9+ (#1673, @nrb)velero install. (#1656, @nrb)velero.io/exclude-from-backup=true label (#1588, @prydonius)velero server and velero restic server commands from the list of available commands as these are not intended for use by the velero CLI user. (#1561, @prydonius)https://github.com/heptio/velero/releases/tag/v1.1.0-beta.2
gcr.io/heptio-images/velero:v1.1.0-beta.2
https://velero.io/docs/v1.1.0-beta.2/
velero backup describe --details (#1741, @prydonius)https://github.com/heptio/velero/releases/tag/v1.1.0-beta.1
gcr.io/heptio-images/velero:v1.1.0-beta.1
https://velero.io/docs/v1.1.0-beta.1/
velero backup create --labels flag (#1729, @prydonius)--secret-file flag on velero install optional, add --no-secret flag for explicit confirmation (#1699, @nrb)velero install and velero plugin add/remove commands will now require Kubernetes 1.9+ (#1673, @nrb)velero install. (#1656, @nrb)velero.io/exclude-from-backup=true label (#1588, @prydonius)velero server and velero restic server commands from the list of available commands as these are not intended for use by the velero CLI user. (#1561, @prydonius)Nothing published for this version
Nothing published for this version
Remove deprecated "hooks" for backups (they've been replaced by "pre hooks") (#1384, @skriss)
velero install, to make it easier to get up and running with Velero. This CLI command replaces the static YAML installation files that were previously part of release tarballs. See the updated install instructions for more information.--log-level flag is now passed to plugin implementationscloud-credentials secret can now be created from a file containing a list of environment variables. Note that velero install always uses this method of providing credentials for Azure. For more details, see Run on Azure.PartiallyFailed, for both backups and restores. This new phase is used for backups/restores that successfully process some but not all of their items.velero migrate-backups command, available in v0.11.1.ubuntu:bionicBlockStore plugins are now named VolumeSnapshotter pluginsgithub.com/heptio/velero/pkg/plugin/frameworkgithub.com/heptio/velero/pkg/plugin/veleroexample.domain.com/plugin-name format
--log-level flag is now passed to all pluginsgcr.io/heptio-images/velero:v1.0.0
https://velero.io/docs/v1.0.0/
To upgrade from a previous version of Velero, see our upgrade instructions.
latest image tag if no version information is provided at build time (#1439, @nrb)restic stats to restic snapshots for checking restic repository existence (#1416, @skriss)AZURE_TENANT_ID=${AZURE_TENANT_ID}
AZURE_SUBSCRIPTION_ID=${AZURE_SUBSCRIPTION_ID}
AZURE_CLIENT_ID=${AZURE_CLIENT_ID}
AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET}
AZURE_RESOURCE_GROUP=${AZURE_RESOURCE_GROUP}
example.io/name. (#1339, @carlisia)velero backup logs & velero restore logs: show helpful error message if backup/restore does not exist or is not finished processing (#1337, @skriss)velero backup get while in progress (#1330, @skriss)velero install command for basic use cases. (#1287, @nrb)velero. (#1264, @carlisia)velero restore to not open every single file open during extraction of the data (#1261, @asaf)describe outputThis is our first release candidate for v1.0. See the All Changes section below for details of changes since v1.0.0-beta.1. We expect this to be the f
This is our first release candidate for v1.0. See the All Changes section below for details of changes since v1.0.0-beta.1. We expect this to be the final release prior to the general availability of v1.0.0. Please try it out in your non-critical environments!
gcr.io/heptio-images/velero:v1.0.0-rc.1
https://heptio.github.io/velero/v1.0.0-rc.1/
velero backup download: check for backup existence before attempting download (#1447, @fabito)backup_last_successful_timestamp prometheus metric (#1448, @fabito)velero install: add --use-volume-snapshots flag to optionally turn off creation of volume snapshot locations (#1462, @nrb)We're excited to release our first beta for v1.0! This beta includes all key features for v1.0 plus a number of bug fixes and documentation updates. S
We're excited to release our first beta for v1.0! This beta includes all key features for v1.0 plus a number of bug fixes and documentation updates. See the All Changes section below for details. Please test it out in your non-critical environments!
We'll continue to fix bugs and make minor changes, and we expect to ship at least one more beta or release candidate prior to the general availability of v1.0.0.
gcr.io/heptio-images/velero:v1.0.0-beta.1
https://heptio.github.io/velero/v1.0.0-beta.1/
restic stats to restic snapshots for checking restic repository existence (#1416, @skriss)latest image tag if no version information is provided at build time (#1439, @nrb)remove deprecated "hooks" for backups (they've been replaced by "pre hooks") (#1384, @skriss)
gcr.io/heptio-images/velero:v1.0.0-alpha.2
Our second v1.0 alpha is ready for testing! Please try it out in your non-critial environments. This alpha contains a bunch of bug fixes and smaller enhancements. See the All Changes section below for details.
We expect that our next release will be v1.0.0-beta.1, meaning that all key features for v1.0.0 will be included. Following that release, we'll continue to fix bugs and make minor improvements, and we expect to ship at least one more beta and/or release candidate prior to the general availability of v1.0.0.
--namespace flag to velero install (@1380, @nrb)storageLocation to be specified as a config parameter for VolumeSnapshotLocations (#1375, @ctrox)backup_total and restore_total (#1353, @fabito)velero install (#1376 #1393 #1394, @nrb and @skriss)remove deprecated code in preparation for v1.0 release:
We're excited to release our first alpha for v1.0! Please take it for a spin in your non-critical environments. Although we've finished the majority of the planned development work for v1.0, we are still working on a handful of items, so don't consider this alpha release to be fully feature-complete. Here's a quick rundown of the major changes in this release:
velero install, to make it easier to get up and running with Velero--log-level flag is now passed to plugin implementationscloud-credentials secret can now be created from a file, whose contents look like the following:AZURE_TENANT_ID=${AZURE_TENANT_ID}
AZURE_SUBSCRIPTION_ID=${AZURE_SUBSCRIPTION_ID}
AZURE_CLIENT_ID=${AZURE_CLIENT_ID}
AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET}
AZURE_RESOURCE_GROUP=${AZURE_RESOURCE_GROUP}
When using this method, the cloud-credentials secret should be mounted as a volume into the Velero deployment and daemon set, at the path /credentials. Additionally, the $AZURE_CREDENTIALS_FILE environment variable should be set to /credentials/cloud (the location of the file within the Velero pods). Note that velero install always uses this method of providing credentials for Azure.debian:stretch-slimBlockStore plugins are now named VolumeSnapshotter pluginsgithub.com/heptio/velero/pkg/plugin/frameworkgithub.com/heptio/velero/pkg/plugin/veleroexample.domain.com/plugin-name format
--log-level flag is now passed to all pluginsexample.io/name. (#1339, @carlisia)velero backup get while in progress (#1330, @skriss)pkg/plugin/velero. (#1264, @carlisia)describe output:
velero install commandhttps://github.com/heptio/velero/releases/tag/v0.11.1
velero migrate-backups command to migrate legacy Ark backup metadata to the current Velero format in object storage. This command needs to be run in preparation for upgrading to v1.0, if you have backups that were originally created prior to v0.11 (i.e. when the project was named Ark).One column per quarter.