velero/site/content/docs/main/upgrade-to-1.18.md

title, layout

title	layout
Upgrading to Velero 1.18	docs

Prerequisites

• Velero v1.17.x installed.

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

• Upgrading to v1.8
• Upgrading to v1.9
• Upgrading to v1.10
• Upgrading to v1.11
• Upgrading to v1.12
• Upgrading to v1.13
• Upgrading to v1.14
• Upgrading to v1.15
• Upgrading to v1.16
• Upgrading to v1.17

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

Instructions

Upgrade from v1.17

1. Install the Velero v1.18 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.18.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 -
   

3. Update the container image used by the Velero deployment, plugin and (optionally) the node agent daemon set:

   # set the container and image of the init container for plugin accordingly,
   # if you are using other plugin
   kubectl set image deployment/velero \
       velero=velero/velero:v1.18.0 \
       velero-plugin-for-aws=velero/velero-plugin-for-aws:v1.14.0 \
       --namespace velero
   
   # optional, if using the node agent daemonset
   kubectl set image daemonset/node-agent \
       node-agent=velero/velero:v1.18.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.18.0
       Git commit: <git SHA>
   
   Server:
       Version: v1.18.0