changelogs/CHANGELOG-1.2.md
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)