Add upgrade doc for v1.13

Add upgrade doc for v1.13

Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

site/content/docs/main/upgrade-to-1.13.md

@@ -1,28 +1,28 @@
 ---
-title: "Upgrading to Velero 1.12"
+title: "Upgrading to Velero 1.13"
 layout: docs
 ---
 
 ## Prerequisites
 
-- Velero [v1.11.x][5] installed.
+- Velero [v1.12.x][5] installed.
 
-If you're not yet running at least Velero v1.7, see the following:
+If you're not yet running at least Velero v1.8, see the following:
 
-- [Upgrading to v1.7][1]
-- [Upgrading to v1.8][2]
-- [Upgrading to v1.9][3]
-- [Upgrading to v1.10][4]
-- [Upgrading to v1.11][5]
+- [Upgrading to v1.8][1]
+- [Upgrading to v1.9][2]
+- [Upgrading to v1.10][3]
+- [Upgrading to v1.11][4]
+- [Upgrading to v1.12][5]
 
 Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero.
 
 ## Instructions
 
-**Caution:** From Velero v1.10, except for using restic to do file-system level backup and restore, kopia is also been integrated, it could be upgraded from v1.10 or higher to v1.12 directly, but it would be a little bit of difference when upgrading to v1.12 from a version lower than v1.10.0. 
+**Caution:** From Velero v1.10, except for using restic to do file-system level backup and restore, kopia is also been integrated, it could be upgraded from v1.10 or higher to v1.13 directly, but it would be a little bit of difference when upgrading to v1.13 from a version lower than v1.10.0. 
 
 ### Upgrade from version lower than v1.10.0
-1. Install the Velero v1.12 command-line interface (CLI) by following the [instructions here][0].
+1. Install the Velero v1.13 command-line interface (CLI) by following the [instructions here][0].
 
     Verify that you've properly installed it by running:
 
@@ -34,7 +34,7 @@ Before upgrading, check the [Velero compatibility matrix](https://github.com/vmw
 
     ```bash
     Client:
-        Version: v1.12.0
+        Version: v1.13.0
         Git commit: <git SHA>
     ```
 
@@ -51,7 +51,7 @@ Before upgrading, check the [Velero compatibility matrix](https://github.com/vmw
     ```bash
     # uploader_type value could be restic or kopia
     kubectl get deploy -n velero -ojson \
-    | sed "s#\"image\"\: \"velero\/velero\:v[0-9]*.[0-9]*.[0-9]\"#\"image\"\: \"velero\/velero\:v1.12.0\"#g" \
+    | sed "s#\"image\"\: \"velero\/velero\:v[0-9]*.[0-9]*.[0-9]\"#\"image\"\: \"velero\/velero\:v1.13.0\"#g" \
     | sed "s#\"server\",#\"server\",\"--uploader-type=$uploader_type\",#g" \
     | sed "s#default-volumes-to-restic#default-volumes-to-fs-backup#g" \
     | sed "s#default-restic-prune-frequency#default-repo-maintain-frequency#g" \
@@ -60,7 +60,7 @@ Before upgrading, check the [Velero compatibility matrix](https://github.com/vmw
 
     # optional, if using the restic daemon set
     echo $(kubectl get ds -n velero restic -ojson) \
-    | sed "s#\"image\"\: \"velero\/velero\:v[0-9]*.[0-9]*.[0-9]\"#\"image\"\: \"velero\/velero\:v1.12.0\"#g" \
+    | sed "s#\"image\"\: \"velero\/velero\:v[0-9]*.[0-9]*.[0-9]\"#\"image\"\: \"velero\/velero\:v1.13.0\"#g" \
     | sed "s#\"name\"\: \"restic\"#\"name\"\: \"node-agent\"#g" \
     | sed "s#\[ \"restic\",#\[ \"node-agent\",#g" \
     | kubectl apply -f -
@@ -77,11 +77,11 @@ Before upgrading, check the [Velero compatibility matrix](https://github.com/vmw
 
     ```bash
     Client:
-        Version: v1.12.0
+        Version: v1.13.0
         Git commit: <git SHA>
 
     Server:
-        Version: v1.12.0
+        Version: v1.13.0
     ```
 
 ### Upgrade from v1.10 or higher
@@ -92,26 +92,26 @@ If it's directly upgraded from v1.10 or higher, the other steps remain the same
    # set the container and image of the init container for plugin accordingly,
    # if you are using other plugin
     kubectl set image deployment/velero \
-        velero=velero/velero:v1.12.0 \
-        velero-plugin-for-aws=velero/velero-plugin-for-aws:v1.8.0 \
+        velero=velero/velero:v1.13.0 \
+        velero-plugin-for-aws=velero/velero-plugin-for-aws:v1.9.0 \
         --namespace velero
 
     # optional, if using the node agent daemonset
     kubectl set image daemonset/node-agent \
-        node-agent=velero/velero:v1.12.0 \
+        node-agent=velero/velero:v1.13.0 \
         --namespace velero
     ```
 
 ## Notes
-If upgraded from v1.9.x, there still remains some resources left over in the cluster and never used in v1.12.x, which could be deleted through kubectl and it is based on your desire:
+If upgraded from v1.9.x, there still remains some resources left over in the cluster and never used in v1.13.x, which could be deleted through kubectl and it is based on your desire:
 
     - resticrepository CRD and related CRs
     - velero-restic-credentials secret in velero install namespace
 
 
 [0]: basic-install.md#install-the-cli
-[1]: https://velero.io/docs/v1.7/upgrade-to-1.7
-[2]: https://velero.io/docs/v1.8/upgrade-to-1.8
-[3]: https://velero.io/docs/v1.9/upgrade-to-1.9
-[4]: https://velero.io/docs/v1.10/upgrade-to-1.10
-[5]: https://velero.io/docs/v1.11/upgrade-to-1.11
+[1]: https://velero.io/docs/v1.8/upgrade-to-1.8
+[2]: https://velero.io/docs/v1.9/upgrade-to-1.9
+[3]: https://velero.io/docs/v1.10/upgrade-to-1.10
+[4]: https://velero.io/docs/v1.11/upgrade-to-1.11
+[5]: https://velero.io/docs/v1.12/upgrade-to-1.12

site/data/docs/main-toc.yml

@@ -13,8 +13,8 @@ toc:
         url: /basic-install
       - page: Customize Installation
         url: /customize-installation
-      - page: Upgrade to 1.12
-        url: /upgrade-to-1.12
+      - page: Upgrade to 1.13
+        url: /upgrade-to-1.13
       - page: Supported providers
         url: /supported-providers
       - page: Evaluation install