Upgrading to Velero 1.4

Prerequisites

• Velero v1.4.2, v1.4.0 or v1.3.x installed.

Note: The v1.4.1 tag was created in code, but has no associated docker image due to misconfigured building infrastructure. v1.4.2 fixed this.

If you’re not yet running at least Velero v1.3, see the following:

• Upgrading to v1.1
• Upgrading to v1.2
• Upgrading to v1.3

Before upgrading, check the Velero compatibility matrix to make sure your version of Kubernetes is supported by the new version of Velero.

Instructions

1. Install the Velero v1.4 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.4.3
       Git commit: <git SHA>
   

2. Update the container image used by the Velero deployment and, optionally, the restic daemon set:

   kubectl set image deployment/velero \
       velero=velero/velero:v1.4.3 \
       --namespace velero
   
   # optional, if using the restic daemon set
   kubectl set image daemonset/restic \
       restic=velero/velero:v1.4.3 \
       --namespace velero
   

3. Update the Velero custom resource definitions (CRDs) to include the new backup progress fields:

   velero install --crds-only --dry-run -o yaml | kubectl apply -f -
   

   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 and issue 2311 for more context.

4. 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.4.3
       Git commit: <git SHA>
   
   Server:
       Version: v1.4.3