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.yamlfile 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.tagunset for every service, includingve.ve-migratorandsurface-migrator. Whenimage.tagis 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-collectorandtags.metricskeys from yourvalidio-values.yamlfile if they are present. Validio 10.0.7 removed the bundled metrics collector. To monitor your deployment, refer to Monitoring VPC Deployments. - Allow your network, or your HTTP proxy, and your users’ browsers to reach
docs.validio.io. Validio reads its in-app release notes from the docs site. Refer to VPC Communication.
Upgrade your Validio version
Use the following command to upgrade Validio:Shell