Skip to main content
This release is built from Vantage Cloud 3.2.1. For the product features, improvements, and fixes in that version, see the Vantage 3.2.1 release notes.

​
Features

​
KEDA autoscaling

Vantage workloads can now scale automatically with KEDA. Autoscaling is off by default. To turn it on, set vantage.keda.enabled to true. KEDA requires Prometheus. For more information, see Autoscaling.

​
Prometheus metrics

The vantage-selfhosted chart can now create Prometheus ServiceMonitor resources that scrape Vantage metrics. To turn this on, set observability.prometheus.serviceMonitor.create to true. For more information, see Prometheus.

​
Improvements

  • Vantage can now run in a service mesh other than Istio, such as Linkerd. When Istio ingress is turned off, the chart no longer creates Istio mTLS resources. For more information, see Configure the service mesh.
  • The chart no longer creates an unused persistent volume claim for folder import. The claim is removed when you upgrade.

​
Fixes

  • Fixed an issue where installation failed preflight validation with the Kubernetes Secrets provider because an Azure Key Vault URI was required. The Key Vault URI is now required only with the Azure Key Vault provider.
  • Fixed an issue where image pulls failed when vantage.ociMigration.destination.repository was set, because the repository appeared twice in image paths.