Add upgrade instructions for v1.7.0

Signed-off-by: Bridget McErlean <bmcerlean@vmware.com>

site/content/docs/main/upgrade-to-1.6.md → site/content/docs/main/upgrade-to-1.7.md

 ---
-title: "Upgrading to Velero 1.6"
+title: "Upgrading to Velero 1.7"
 layout: docs
 ---
 
 ## Prerequisites
 
-- Velero [v1.5.x][5] installed.
+- Velero [v1.6.x][6] installed.
 
-If you're not yet running at least Velero v1.5, see the following:
+If you're not yet running at least Velero v1.6, see the following:
 
 - [Upgrading to v1.1][1]
 - [Upgrading to v1.2][2]
 - [Upgrading to v1.3][3]
 - [Upgrading to v1.4][4]
 - [Upgrading to v1.5][5]
+- [Upgrading to v1.6][6]
 
 ## Instructions
 
-1. Install the Velero v1.6 command-line interface (CLI) by following the [instructions here][0].
+1. Install the Velero v1.7 command-line interface (CLI) by following the [instructions here][0].
 
     Verify that you've properly installed it by running:
 
@@ -29,7 +30,7 @@ If you're not yet running at least Velero v1.5, see the following:
 
     ```bash
     Client:
-        Version: v1.6.2
+        Version: v1.7.0
         Git commit: <git SHA>
     ```
 
@@ -41,18 +42,18 @@ If you're not yet running at least Velero v1.5, see the following:
 
     **NOTE:** You could change the default CRD API version (v1beta1 _or_ v1) if Velero CLI can't discover the Kubernetes preferred CRD API version. The Kubernetes version < 1.16 preferred CRD API version is v1beta1; the Kubernetes version >= 1.16 preferred CRD API version is v1.
 
-    **NOTE:** If you are upgrading Velero in Kubernetes 1.14.x or earlier, you will need to use `kubectl apply`'s `--validate=false` option when applying the CRD configuration above. See [issue 2077][6] and [issue 2311][7] for more context.
+    **NOTE:** If you are upgrading Velero in Kubernetes 1.14.x or earlier, you will need to use `kubectl apply`'s `--validate=false` option when applying the CRD configuration above. See [issue 2077][10] and [issue 2311][11] for more context.
 
 1. Update the container image used by the Velero deployment and, optionally, the restic daemon set:
 
     ```bash
     kubectl set image deployment/velero \
-        velero=velero/velero:v1.6.2 \
+        velero=velero/velero:v1.7.0 \
         --namespace velero
 
     # optional, if using the restic daemon set
     kubectl set image daemonset/restic \
-        restic=velero/velero:v1.6.2 \
+        restic=velero/velero:v1.7.0 \
         --namespace velero
     ```
 
@@ -66,11 +67,11 @@ If you're not yet running at least Velero v1.5, see the following:
 
     ```bash
     Client:
-        Version: v1.6.2
+        Version: v1.7.0
         Git commit: <git SHA>
 
     Server:
-        Version: v1.6.2
+        Version: v1.7.0
     ```
 
 ## Notes
@@ -85,7 +86,7 @@ After upgrading, if there is a previously created backup storage location with t
 [3]: https://velero.io/docs/v1.3.2/upgrade-to-1.3/
 [4]: https://velero.io/docs/v1.4/upgrade-to-1.4/
 [5]: https://velero.io/docs/v1.5/upgrade-to-1.5
-[6]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2
-[7]: https://github.com/vmware-tanzu/velero/issues/2077
-[8]: https://github.com/vmware-tanzu/velero/issues/2311
-[9]: https://velero.io/docs/v1.6/locations
+[6]: https://velero.io/docs/v1.6/upgrade-to-1.6
+[9]: https://velero.io/docs/v1.7/locations
+[10]: https://github.com/vmware-tanzu/velero/issues/2077
+[11]: https://github.com/vmware-tanzu/velero/issues/2311

site/content/docs/v1.7/upgrade-to-1.6.md → site/content/docs/v1.7/upgrade-to-1.7.md

 ---
-title: "Upgrading to Velero 1.6"
+title: "Upgrading to Velero 1.7"
 layout: docs
 ---
 
 ## Prerequisites
 
-- Velero [v1.5.x][5] installed.
+- Velero [v1.6.x][6] installed.
 
-If you're not yet running at least Velero v1.5, see the following:
+If you're not yet running at least Velero v1.6, see the following:
 
 - [Upgrading to v1.1][1]
 - [Upgrading to v1.2][2]
 - [Upgrading to v1.3][3]
 - [Upgrading to v1.4][4]
 - [Upgrading to v1.5][5]
+- [Upgrading to v1.6][6]
 
 ## Instructions
 
-1. Install the Velero v1.6 command-line interface (CLI) by following the [instructions here][0].
+1. Install the Velero v1.7 command-line interface (CLI) by following the [instructions here][0].
 
     Verify that you've properly installed it by running:
 
@@ -29,7 +30,7 @@ If you're not yet running at least Velero v1.5, see the following:
 
     ```bash
     Client:
-        Version: v1.6.2
+        Version: v1.7.0
         Git commit: <git SHA>
     ```
 
@@ -41,18 +42,18 @@ If you're not yet running at least Velero v1.5, see the following:
 
     **NOTE:** You could change the default CRD API version (v1beta1 _or_ v1) if Velero CLI can't discover the Kubernetes preferred CRD API version. The Kubernetes version < 1.16 preferred CRD API version is v1beta1; the Kubernetes version >= 1.16 preferred CRD API version is v1.
 
-    **NOTE:** If you are upgrading Velero in Kubernetes 1.14.x or earlier, you will need to use `kubectl apply`'s `--validate=false` option when applying the CRD configuration above. See [issue 2077][6] and [issue 2311][7] for more context.
+    **NOTE:** If you are upgrading Velero in Kubernetes 1.14.x or earlier, you will need to use `kubectl apply`'s `--validate=false` option when applying the CRD configuration above. See [issue 2077][10] and [issue 2311][11] for more context.
 
 1. Update the container image used by the Velero deployment and, optionally, the restic daemon set:
 
     ```bash
     kubectl set image deployment/velero \
-        velero=velero/velero:v1.6.2 \
+        velero=velero/velero:v1.7.0 \
         --namespace velero
 
     # optional, if using the restic daemon set
     kubectl set image daemonset/restic \
-        restic=velero/velero:v1.6.2 \
+        restic=velero/velero:v1.7.0 \
         --namespace velero
     ```
 
@@ -66,11 +67,11 @@ If you're not yet running at least Velero v1.5, see the following:
 
     ```bash
     Client:
-        Version: v1.6.2
+        Version: v1.7.0
         Git commit: <git SHA>
 
     Server:
-        Version: v1.6.2
+        Version: v1.7.0
     ```
 
 ## Notes
@@ -85,7 +86,7 @@ After upgrading, if there is a previously created backup storage location with t
 [3]: https://velero.io/docs/v1.3.2/upgrade-to-1.3/
 [4]: https://velero.io/docs/v1.4/upgrade-to-1.4/
 [5]: https://velero.io/docs/v1.5/upgrade-to-1.5
-[6]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2
-[7]: https://github.com/vmware-tanzu/velero/issues/2077
-[8]: https://github.com/vmware-tanzu/velero/issues/2311
-[9]: https://velero.io/docs/v1.6/locations
+[6]: https://velero.io/docs/v1.6/upgrade-to-1.6
+[9]: https://velero.io/docs/v1.7/locations
+[10]: https://github.com/vmware-tanzu/velero/issues/2077
+[11]: https://github.com/vmware-tanzu/velero/issues/2311