Skip to main content
Vantage 3.0 self-hosted upgrades are operator-driven. Upgrade the vantage-operator and vantage-selfhosted Helm releases to the same new version. The new vantage-selfhosted chart references a versioned workloads ConfigMap, which causes the operator to reprocess the Vantage resource and reconcile the matching Vantage release. Automatic upgrades are not yet implemented.

Upgrade workflow

The operator and Vantage charts are released together and must remain version-aligned. Installing the new operator prepares the compatible controller and CRD; installing the matching vantage-selfhosted chart updates the versioned workloads ConfigMap reference and triggers the in-place update. To perform the upgrade:
1

Review the release notes

Read the release notes for every release between your installed version and the target release, and apply each Breaking changes item to your values before you upgrade. Use the chart version listed in the release notes as $new_version (for example, 0.84.29 for release 2026.10.02). The date-based release label is not a chart version.
2

Check the installed version

Confirm the chart versions currently installed, and the release version the Vantage resource declares in spec.vantageVersion:
The vantage-selfhosted chart sets spec.vantageVersion from its app version. status.installedVantageVersion is not populated by the current operator.
3

Upgrade both charts

Upgrade the operator first, then upgrade the vantage-selfhosted release to the same version.
If you use GitOps, update both chart revisions to the same version and let your controller render them with your existing values source.
4

Wait for the resource to reconcile

Wait for the operator to pick up the new spec, then wait for Ready. Until the operator observes the change, Ready still reports the previous version, so waiting on Ready alone can return immediately:
For finer-grained visibility, watch the OCI migration job and ArgoCD application sync status. Skill installation runs as a separate job that ArgoCD does not track; see Lifecycle. If a chart fails to reconcile, the operator surfaces the cause in status.degradationReasons[].

What’s different from Vantage 2.7

In Vantage 2.7 self-hosted, an upgrade meant running the Ansible installer container against an updated values file and letting it helm upgrade every chart in sequence, an operation that touched both infrastructure and application configuration in one step. In 3.0, the application upgrade is decoupled from infrastructure changes: The 2.7 installer model is not supported in 3.0, and there is no in-place upgrade from 2.7. Moving from 2.7 is a migration; see Migrate from Vantage 2.7. The Vantage chart upgrades cover Vantage Core only: software you installed separately, such as your monitoring stack, is upgraded by you on your own schedule.

What’s next

Architecture

What the operator does on every reconcile.

Known Limitations

Constraints to be aware of before planning an upgrade window.