v1.2 release

CHANGELOG.md

@@ -1,11 +1,11 @@
 ## Current release:
-  * [CHANGELOG-1.1.md][11]
+  * [CHANGELOG-1.2.md][12]
 
 ## Development release:
-  * [v1.2.0-beta.1][12]
   * [Unreleased Changes][0]
 
 ## Older releases:
+  * [CHANGELOG-1.1.md][11]
   * [CHANGELOG-1.0.md][10]
   * [CHANGELOG-0.11.md][9]
   * [CHANGELOG-0.10.md][8]

changelogs/CHANGELOG-1.2.md

@@ -1,40 +1,60 @@
-## v1.2.0-beta.1
-#### 2019-10-24
+## v1.2.0
+#### 2019-11-07
 
 ### Download
-- https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0-beta.1
+https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0
 
 ### Container Image
-`velero/velero:v1.2.0-beta.1`
+`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.
 
 ### Documentation
-https://velero.io/docs/v1.2.0-beta.1/
+https://velero.io/docs/v1.2.0/
 
 ### Upgrading
+https://velero.io/docs/v1.2.0/upgrade-to-1.2/
+
+### Highlights
+## Moving Cloud Provider Plugins Out of Tree
 
-If you're upgrading from a previous version of Velero, there are several changes you'll need to be aware of:
+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.
 
-- Container images are now published to Docker Hub. To upgrade your server, use the new image `velero/velero:v1.2.0-beta.1`.
-- The AWS, Microsoft Azure, and GCP provider plugins that were previously part of the Velero binary have been extracted to their own standalone repositories/plugin images. If you are using one of these three providers, you will need to explicitly add the appropriate plugin to your Velero install:
-  - [AWS] `velero plugin add velero/velero-plugin-for-aws:v1.0.0-beta.1`
-  - [Azure] `velero plugin add velero/velero-plugin-for-microsoft-azure:v1.0.0-beta.1`
-  - [GCP] `velero plugin add velero/velero-plugin-for-gcp:v1.0.0-beta.1`
+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.
 
-### Highlights
+## Restic Integration Improvements
+
+We’ve continued to work on improving Velero’s restic integration. With this release, we’ve made the following enhancements:
+
+- Restic backup and restore progress is now captured during execution and visible to the user through the `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.
+- Restic backups of persistent volume claims (PVCs) now remain incremental across the rescheduling of a pod. Previously, if the pod using a PVC was rescheduled, the next restic backup would require a full rescan of the volume’s contents. This improvement potentially makes such backups significantly faster.
+- Read-write-many volumes are no longer backed up once for every pod using the volume, but instead just once per Velero backup. This improvement speeds up backups and prevents potential restore issues due to multiple copies of the backup being processed simultaneously.
+
+
+## Clone PVs When Cloning a Namespace
 
-- The AWS, Microsoft Azure, and GCP provider plugins that were previously part of the Velero binary have been extracted to their own standalone repositories/plugin images. They now function like any other provider plugin.
-- Container images are now published to Docker Hub: `velero/velero:v1.2.0-beta.1`.
-- Several improvements have been made to the restic integration:
-  - Backup and restore progress is now updated on the `PodVolumeBackup` and `PodVolumeRestore` custom resources and viewable via `velero backup/restore describe` while operations are in progress.
-  - Read-write-many PVCs are now only backed up once.
-  - Backups of PVCs remain incremental across pod reschedules.
-- A structural schema has been added to the Velero CRDs that are created by `velero install` to enable validation of API fields.
-- During restores that use the `--namespace-mappings` flag to clone a namespace within a cluster, PVs will now be cloned as needed.
+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.
+
+## Improved Server-Side Encryption Support
+
+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:
+- On AWS, Velero now supports Amazon S3-managed encryption keys (SSE-S3), which uses AES256 encryption, by specifying `serverSideEncryption: AES256` in a backup storage location’s config.
+- On GCP, Velero now supports using a specific Cloud KMS key for server-side encryption by specifying `kmsKeyName: <key name>` in a backup storage location’s config.
+
+## CRD Structural Schema
+
+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.
 
 ### All Changes
+  * Ensure object store plugin processes are cleaned up after restore and after BSL validation during server start up (#2041, @betta1)
+  * bug fix: don't try to restore pod volume backups that don't have a snapshot ID (#2031, @skriss)
+  * Restore Documentation: Updated Restore Documentation with Clarification implications of removing restore object. (#1957, @nainav)
+  * add `--allow-partially-failed` flag to `velero restore create` for use with `--from-schedule` to allow partially-failed backups to be restored (#1994, @skriss)
   * Allow backup storage locations to specify backup sync period or toggle off sync (#1936, @betta1)
   * Remove cloud provider code (#1985, @carlisia)
-  * Restore action for cluster/namespace role bindings (#1974, @alexander)
+  * Restore action for cluster/namespace role bindings (#1974, @alexander-demichev)
   * Add `--no-default-backup-location` flag to `velero install` (#1931, @Frank51)
   * If includeClusterResources is nil/auto, pull in necessary CRDs in backupResource (#1831, @sseago)
   * Azure: add support for Azure China/German clouds (#1938, @andyzhangx)
@@ -61,4 +81,3 @@ If you're upgrading from a previous version of Velero, there are several changes
   * fix error formatting due interpreting % as printf formatted strings (#1781, @s12chung)
   * when using `velero restore create --namespace-mappings ...` to create a second copy of a namespace in a cluster, create copies of the PVs used (#1779, @skriss)
   * adds --from-schedule flag to the `velero create backup` command to create a Backup from an existing Schedule (#1734, @prydonius)
-  * add `--allow-partially-failed` flag to `velero restore create` for use with `--from-schedule` to allow partially-failed backups to be restored (#1994, @skriss)

site/_config.yml

@@ -56,10 +56,10 @@ defaults:
       gh: https://github.com/vmware-tanzu/velero/tree/master
       layout: "docs"
   - scope:
-      path: docs/v1.2.0-beta.1
+      path: docs/v1.2.0
     values:
-      version: v1.2.0-beta.1
-      gh: https://github.com/vmware-tanzu/velero/tree/v1.2.0-beta.1
+      version: v1.2.0
+      gh: https://github.com/vmware-tanzu/velero/tree/v1.2.0
       layout: "docs"
   - scope:
       path: docs/v1.1.0
@@ -151,10 +151,10 @@ collections:
   - casestudies
 
 versioning: true
-latest: v1.1.0
+latest: v1.2.0
 versions:
 - master
-- v1.2.0-beta.1
+- v1.2.0
 - v1.1.0
 - v1.0.0
 - v0.11.0

site/_data/toc-mapping.yml

@@ -3,7 +3,7 @@
 # that the navigation for older versions still work.
 
 master: master-toc
-v1.2.0-beta.1: v1-2-0-beta-1-toc
+v1.2.0: v1-2-0-toc
 v1.1.0: v1-1-0-toc
 v1.0.0: v1-0-0-toc
 v0.11.0: v011-toc

site/_data/v1-2-0-beta-1-toc.yml → site/_data/v1-2-0-toc.yml

@@ -11,8 +11,8 @@ toc:
     subfolderitems:
       - page: Overview
         url: /install-overview
-      - page: Upgrade to 1.1
-        url: /upgrade-to-1.1
+      - page: Upgrade to 1.2
+        url: /upgrade-to-1.2
       - page: Supported providers
         url: /supported-providers
       - page: Evaluation install 
@@ -63,6 +63,10 @@ toc:
         url: /build-from-source
       - page: Run locally
         url: /run-locally
+      - page: Code standards
+        url: /code-standards
+      - page: Website guidelines
+        url: /website-guidelines
   - title: More information
     subfolderitems:
       - page: Backup file format