From 73ee80f17eced8f18002957f8278198843d46c46 Mon Sep 17 00:00:00 2001 From: Steve Kriss Date: Mon, 24 Feb 2020 14:21:22 -0700 Subject: [PATCH] update upgrade instructions for v1.3 Signed-off-by: Steve Kriss --- site/docs/master/upgrade-to-1.2.md | 102 ---------------------- site/docs/master/upgrade-to-1.3.md | 63 +++++++++++++ site/docs/v1.3.0-beta.2/upgrade-to-1.2.md | 102 ---------------------- site/docs/v1.3.0-beta.2/upgrade-to-1.3.md | 63 +++++++++++++ 4 files changed, 126 insertions(+), 204 deletions(-) delete mode 100644 site/docs/master/upgrade-to-1.2.md create mode 100644 site/docs/master/upgrade-to-1.3.md delete mode 100644 site/docs/v1.3.0-beta.2/upgrade-to-1.2.md create mode 100644 site/docs/v1.3.0-beta.2/upgrade-to-1.3.md diff --git a/site/docs/master/upgrade-to-1.2.md b/site/docs/master/upgrade-to-1.2.md deleted file mode 100644 index 583ce85e6..000000000 --- a/site/docs/master/upgrade-to-1.2.md +++ /dev/null @@ -1,102 +0,0 @@ -# Upgrading to Velero 1.2 - -## Prerequisites - -- Velero [v1.1][0] or [v1.0][1] installed. - -_Note: if you're upgrading from v1.0, follow the [upgrading to v1.1][2] instructions first._ - -## Instructions - -1. Install the Velero v1.2 command-line interface (CLI) by following the [instructions here][3]. - - Verify that you've properly installed it by running: - - ```bash - velero version --client-only - ``` - - You should see the following output: - - ```bash - Client: - Version: v1.2.0 - Git commit: - ``` - -1. Scale down the existing Velero deployment: - - ```bash - kubectl scale deployment/velero \ - --namespace velero \ - --replicas 0 - ``` - -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.2.0 \ - --namespace velero - - # optional, if using the restic daemon set - kubectl set image daemonset/restic \ - restic=velero/velero:v1.2.0 \ - --namespace velero - ``` - -1. If using AWS, Azure, or GCP, add the respective plugin to your Velero deployment: - - For AWS: - - ```bash - velero plugin add velero/velero-plugin-for-aws:v1.0.0 - ``` - - For Azure: - - ```bash - velero plugin add velero/velero-plugin-for-microsoft-azure:v1.0.0 - ``` - - For GCP: - - ```bash - velero plugin add velero/velero-plugin-for-gcp:v1.0.0 - ``` - -1. Update the Velero custom resource definitions (CRDs) to include the structural schemas: - - ```bash - velero install --crds-only --dry-run -o yaml | kubectl apply -f - - ``` - -1. Scale back up the existing Velero deployment: - - ```bash - kubectl scale deployment/velero \ - --namespace velero \ - --replicas 1 - ``` - -1. Confirm that the deployment is up and running with the correct version by running: - - ```bash - velero version - ``` - - You should see the following output: - - ```bash - Client: - Version: v1.2.0 - Git commit: - - Server: - Version: v1.2.0 - ``` - -[0]: https://github.com/vmware-tanzu/velero/releases/tag/v1.1.0 -[1]: https://github.com/vmware-tanzu/velero/releases/tag/v1.0.0 -[2]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ -[3]: basic-install.md#install-the-cli diff --git a/site/docs/master/upgrade-to-1.3.md b/site/docs/master/upgrade-to-1.3.md new file mode 100644 index 000000000..528852e25 --- /dev/null +++ b/site/docs/master/upgrade-to-1.3.md @@ -0,0 +1,63 @@ +# Upgrading to Velero 1.3 + +## Prerequisites + +- Velero [v1.2][3] installed. + +If you're not yet running Velero v1.2, see the following: + +- [Upgrading to v1.1][1] +- [Upgrading to v1.2][2] + +## Instructions + +1. Install the Velero v1.3 command-line interface (CLI) by following the [instructions here][0]. + + Verify that you've properly installed it by running: + + ```bash + velero version --client-only + ``` + + You should see the following output: + + ```bash + Client: + Version: v1.3.0 + Git commit: + ``` + +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.3.0 \ + --namespace velero + + # optional, if using the restic daemon set + kubectl set image daemonset/restic \ + restic=velero/velero:v1.3.0 \ + --namespace velero + ``` + +1. Confirm that the deployment is up and running with the correct version by running: + + ```bash + velero version + ``` + + You should see the following output: + + ```bash + Client: + Version: v1.3.0 + Git commit: + + Server: + Version: v1.3.0 + ``` + +[0]: basic-install.md#install-the-cli +[1]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ +[2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ +[3]: https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0 diff --git a/site/docs/v1.3.0-beta.2/upgrade-to-1.2.md b/site/docs/v1.3.0-beta.2/upgrade-to-1.2.md deleted file mode 100644 index 583ce85e6..000000000 --- a/site/docs/v1.3.0-beta.2/upgrade-to-1.2.md +++ /dev/null @@ -1,102 +0,0 @@ -# Upgrading to Velero 1.2 - -## Prerequisites - -- Velero [v1.1][0] or [v1.0][1] installed. - -_Note: if you're upgrading from v1.0, follow the [upgrading to v1.1][2] instructions first._ - -## Instructions - -1. Install the Velero v1.2 command-line interface (CLI) by following the [instructions here][3]. - - Verify that you've properly installed it by running: - - ```bash - velero version --client-only - ``` - - You should see the following output: - - ```bash - Client: - Version: v1.2.0 - Git commit: - ``` - -1. Scale down the existing Velero deployment: - - ```bash - kubectl scale deployment/velero \ - --namespace velero \ - --replicas 0 - ``` - -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.2.0 \ - --namespace velero - - # optional, if using the restic daemon set - kubectl set image daemonset/restic \ - restic=velero/velero:v1.2.0 \ - --namespace velero - ``` - -1. If using AWS, Azure, or GCP, add the respective plugin to your Velero deployment: - - For AWS: - - ```bash - velero plugin add velero/velero-plugin-for-aws:v1.0.0 - ``` - - For Azure: - - ```bash - velero plugin add velero/velero-plugin-for-microsoft-azure:v1.0.0 - ``` - - For GCP: - - ```bash - velero plugin add velero/velero-plugin-for-gcp:v1.0.0 - ``` - -1. Update the Velero custom resource definitions (CRDs) to include the structural schemas: - - ```bash - velero install --crds-only --dry-run -o yaml | kubectl apply -f - - ``` - -1. Scale back up the existing Velero deployment: - - ```bash - kubectl scale deployment/velero \ - --namespace velero \ - --replicas 1 - ``` - -1. Confirm that the deployment is up and running with the correct version by running: - - ```bash - velero version - ``` - - You should see the following output: - - ```bash - Client: - Version: v1.2.0 - Git commit: - - Server: - Version: v1.2.0 - ``` - -[0]: https://github.com/vmware-tanzu/velero/releases/tag/v1.1.0 -[1]: https://github.com/vmware-tanzu/velero/releases/tag/v1.0.0 -[2]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ -[3]: basic-install.md#install-the-cli diff --git a/site/docs/v1.3.0-beta.2/upgrade-to-1.3.md b/site/docs/v1.3.0-beta.2/upgrade-to-1.3.md new file mode 100644 index 000000000..207f76b5f --- /dev/null +++ b/site/docs/v1.3.0-beta.2/upgrade-to-1.3.md @@ -0,0 +1,63 @@ +# Upgrading to Velero 1.3 + +## Prerequisites + +- Velero [v1.2][3] installed. + +If you're not yet running Velero v1.2, see the following: + +- [Upgrading to v1.1][1] +- [Upgrading to v1.2][2] + +## Instructions + +1. Install the Velero v1.3 command-line interface (CLI) by following the [instructions here][0]. + + Verify that you've properly installed it by running: + + ```bash + velero version --client-only + ``` + + You should see the following output: + + ```bash + Client: + Version: v1.3.0-beta.2 + Git commit: + ``` + +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.3.0-beta.2 \ + --namespace velero + + # optional, if using the restic daemon set + kubectl set image daemonset/restic \ + restic=velero/velero:v1.3.0-beta.2 \ + --namespace velero + ``` + +1. Confirm that the deployment is up and running with the correct version by running: + + ```bash + velero version + ``` + + You should see the following output: + + ```bash + Client: + Version: v1.3.0-beta.2 + Git commit: + + Server: + Version: v1.3.0-beta.2 + ``` + +[0]: basic-install.md#install-the-cli +[1]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ +[2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ +[3]: https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0