Skip to main content
This guide discusses how to upgrade Validio in a self-managed VPC deployment. For installation instructions, refer to VPC Deployment Installation.

​
Before you upgrade

When upgrading the Validio version in your VPC deployment, you should:
  • Always take a backup immediately before you upgrade. A restore from that backup is the only supported way to recover from a failed upgrade. Refer to Backing up VPC Deployments.
  • Always upgrade one major version at a time to ensure that the migrations succeed. For example, you should upgrade from 6.x —> 7.x, but not 5.x —> 7.x. For a list of major Validio versions, refer to the Platform Requirements guide.
  • Ensure that you use the correct validio-values.yaml file when upgrading Validio. Otherwise, you risk changing your configuration.
  • Ensure that you are running compatible versions of the platform and SDK. Refer to the Platform and SDK Compatibility table.
  • Leave image.tag unset for every service, including ve.ve-migrator and surface-migrator. When image.tag is unset, each service uses the image version that matches the Helm chart version you install. If you pin a tag, that service keeps running the pinned image after you upgrade, and its version no longer matches the other services.
  • Remove the otel-collector and tags.metrics keys from your validio-values.yaml file if they are present. Validio 10.0.7 removed the bundled metrics collector. To monitor your deployment, refer to Monitoring VPC Deployments.
Rollback is not supportedUpgrades are one-way. Once you have upgraded, returning to an earlier Validio version is not supported, and you should not attempt a Helm rollback.To recover from a failed upgrade, restore the backup you took before the upgrade, into the same Validio version that the backup was taken at. Refer to Backing up VPC Deployments.

​
Upgrade your Validio version

Use the following command to upgrade Validio:
Shell