2.3 KiB
title | layout |
---|---|
Upgrading to Velero 1.2 | docs |
Prerequisites
Note: if you're upgrading from v1.0, follow the upgrading to v1.1 instructions first.
Instructions
-
Install the Velero v1.2 command-line interface (CLI) by following the instructions here.
Verify that you've properly installed it by running:
velero version --client-only
You should see the following output:
Client: Version: v1.2.0 Git commit: <git SHA>
-
Scale down the existing Velero deployment:
kubectl scale deployment/velero \ --namespace velero \ --replicas 0
-
Update the container image used by the Velero deployment and, optionally, the restic daemon set:
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
-
If using AWS, Azure, or GCP, add the respective plugin to your Velero deployment:
For AWS:
velero plugin add velero/velero-plugin-for-aws:v1.0.0
For Azure:
velero plugin add velero/velero-plugin-for-microsoft-azure:v1.0.0
For GCP:
velero plugin add velero/velero-plugin-for-gcp:v1.0.0
-
Update the Velero custom resource definitions (CRDs) to include the structural schemas:
velero install --crds-only --dry-run -o yaml | kubectl apply -f -
-
Scale back up the existing Velero deployment:
kubectl scale deployment/velero \ --namespace velero \ --replicas 1
-
Confirm that the deployment is up and running with the correct version by running:
velero version
You should see the following output:
Client: Version: v1.2.0 Git commit: <git SHA> Server: Version: v1.2.0