From b9f42822012af68b4e162732c1a61b326fb20663 Mon Sep 17 00:00:00 2001 From: Steve Kriss Date: Wed, 6 Nov 2019 15:33:59 -0700 Subject: [PATCH] fix alignment/numbering on upgrade instructions Signed-off-by: Steve Kriss --- site/docs/master/upgrade-to-1.2.md | 116 +++++++++++++++-------------- site/docs/v1.2.0/upgrade-to-1.2.md | 116 +++++++++++++++-------------- 2 files changed, 118 insertions(+), 114 deletions(-) diff --git a/site/docs/master/upgrade-to-1.2.md b/site/docs/master/upgrade-to-1.2.md index 810844eff..4e2d86a64 100644 --- a/site/docs/master/upgrade-to-1.2.md +++ b/site/docs/master/upgrade-to-1.2.md @@ -6,91 +6,93 @@ _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: + Verify that you've properly installed it by running: - ```bash - velero version --client-only - ``` + ```bash + velero version --client-only + ``` - You should see the following output: - - ```bash - Client: - Version: v1.2.0 - Git commit: - ``` + 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 - ``` + ```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 + ```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 - ``` + # 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 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 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 - ``` + 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 - - ``` + ```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 - ``` + ```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 - ``` + ```bash + velero version + ``` - You should see the following output: + You should see the following output: - ```bash - Client: - Version: v1.2.0 - Git commit: + ```bash + Client: + Version: v1.2.0 + Git commit: - Server: - Version: v1.2.0 - ``` + Server: + Version: v1.2.0 + ``` [0]: https://github.com/vmware-tanzu/velero/releases/tag/v1.1.0 diff --git a/site/docs/v1.2.0/upgrade-to-1.2.md b/site/docs/v1.2.0/upgrade-to-1.2.md index 810844eff..e8cb0f661 100644 --- a/site/docs/v1.2.0/upgrade-to-1.2.md +++ b/site/docs/v1.2.0/upgrade-to-1.2.md @@ -6,91 +6,93 @@ _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: + Verify that you've properly installed it by running: - ```bash - velero version --client-only - ``` + ```bash + velero version --client-only + ``` - You should see the following output: - - ```bash - Client: - Version: v1.2.0 - Git commit: - ``` + 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 - ``` + ```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 + ```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 - ``` + # 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 AWS: - For Azure: - ```bash - velero plugin add velero/velero-plugin-for-microsoft-azure:v1.0.0 - ``` + ```bash + velero plugin add velero/velero-plugin-for-aws:v1.0.0 + ``` - For GCP: - ```bash - velero plugin add velero/velero-plugin-for-gcp: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 - - ``` + ```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 - ``` + ```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 - ``` + ```bash + velero version + ``` - You should see the following output: + You should see the following output: - ```bash - Client: - Version: v1.2.0 - Git commit: + ```bash + Client: + Version: v1.2.0 + Git commit: - Server: - Version: v1.2.0 - ``` + Server: + Version: v1.2.0 + ``` [0]: https://github.com/vmware-tanzu/velero/releases/tag/v1.1.0