> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vantage self-hosted 2026.08.25 release notes

> ABBYY Vantage self-hosted 2026.08.25, built from Vantage Cloud 3.4.0: a new Istio mesh setting, support for TLS-terminating reverse proxies, the Analytics UI follows the reportingEnabled setting, custom labels and annotations for the Istio Gateway, and upcoming ingress default changes.

This release is built from Vantage Cloud 3.4.0. For the product features, improvements, and fixes in that version, see the [Vantage 3.4.0 release notes](https://docs.abbyy.com/vantage/release-notes/3-4-0.md).

## Artifact versions

| Artifact | Version |
| - | - |
| `vantage-operator` chart | `0.77.14` |
| `vantage-selfhosted` chart | `0.77.14` |
| `vantage-operator` image | `v0.77.14` |

## Breaking changes

### Istio mesh setting

Istio mesh resources are now controlled by `mesh.istio.enabled` (default `true`) instead of the ingress settings. If you don't use Istio, for example on self-managed Kubernetes with Linkerd, set `mesh.istio.enabled: false` before you upgrade.

## Features

### TLS-terminating reverse proxies

When an ingress controller or proxy terminates TLS, set `vantage.reverseProxy` to `true` so that sign-in uses `https://` addresses.

For more information, see [Forwarded HTTPS scheme](https://docs.abbyy.com/vantage/self-hosted/v3.0/providers/self-managed.md#forwarded-https-scheme).

## Improvements

* The Analytics screens now follow the `vantage.reportingEnabled` value and are hidden unless it is set to `true`. For more information, see the [Vantage 3.3.0 release notes](https://docs.abbyy.com/vantage/release-notes/3-3-0.md).

* You can now add custom labels and annotations to the Istio Gateway with `ingress.istio.gateway.labels` and `ingress.istio.gateway.annotations`.

## Upcoming changes

* In a future major version, the `vantage-selfhosted` chart will no longer default to Istio ingress. If you use Istio ingress, set `ingress.type: istio` and `mesh.istio.enabled: true` in your values now so your configuration is not affected.