Documentation

Upgrading to Velero 1.6

Prerequisites

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

Instructions

  1. Install the Velero v1.6 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.6.0
        Git commit: <git SHA>
    
  2. Update the Velero custom resource definitions (CRDs) to include schema changes across all CRDs that are at the core of the new features in this release:

    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.

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

    kubectl set image deployment/velero \
        velero=velero/velero:v1.6.0 \
        --namespace velero
    
    # optional, if using the restic daemon set
    kubectl set image daemonset/restic \
        restic=velero/velero:v1.6.0 \
        --namespace velero
    
  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.6.0
        Git commit: <git SHA>
    
    Server:
        Version: v1.6.0
    

Notes

Default backup storage location

We have deprecated the way to indicate the default backup storage location. Previously, that was indicated according to the backup storage location name set on the velero server-side via the flag velero server --default-backup-storage-location. Now we configure the default backup storage location on the velero client-side. Please refer to the About locations on how to indicate which backup storage location is the default one.

After upgrading, if there is a previously created backup storage location with the name that matches what was defined on the server side as the default, it will be automatically set as the default.

Getting Started

To help you get started, see the documentation.