# Emissary-Ingress v3.10.0

2025-07-29 · [Original release notes](https://github.com/emissary-ingress/emissary/releases/tag/v3.10.0) · [Full summary](https://ratatosk.io/en/releases/emissary-ingress/v3.10.0)

Breaking changes 2 · Important fixes 1 · Enhancements 1 · Dependency updates 3 · Other changes 5

## Check before upgrading

### Upgrade guide

- **Quickstart for fresh installs and upgrades**
  >     See the [Quickstart](https://emissary-ingress.dev/docs/3.10/quick-start/) for more details.

## Breaking changes (2)

### Published YAML manifests no longer install the Ambassador Agent by default

- Affects: Emissary-ingress installations from published YAML manifests

The Ambassador Agent provides additional features on top of Emissary-ingress.

> - Change: Emissary-ingress will no longer publish YAML manifest with the Ambassador Agent being
>   installed by default. This is an optional component that provides additional features on top of
>   Emissary-ingress and we recommend installing it using the instructions found in the <a
>   href="https://github.com/datawire/ambassador-agenty">Ambassador Agent Repo</a>.

https://github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

### Emissary image and Helm charts listed at GHCR

- Affects: Emissary image or Helm chart deployments (Inferred)

Emissary images were hosted on DockerHub. This release lists the main image at `ghcr.io/emissary-ingress/emissary:3.10.0` and the CRD and control-plane charts at `ghcr.io/emissary-ingress/emissary-crds-charts` and `ghcr.io/emissary-ingress/emissary-chart`; the note does not state the charts’ previous locations.

> - Change: The Emissary images are now hosted at GHCR rather than at DockerHub.
>     - The main Emissary image is at `ghcr.io/emissary-ingress/emissary:3.10.0`
>     - The (new) Helm chart for the Emissary CRDs is at `ghcr.io/emissary-ingress/emissary-crds-charts`
>     - The Helm chart for the Emissary control plane is at `ghcr.io/emissary-ingress/emissary-chart`

## Important fixes (1)

### MD5 panic in `ambex` route hashing fixed

- Affects: Emissary installations using `ambex` to convert V3 listeners to RDS listeners (Inferred)

In crypto-restricted environments such as FIPS, `ambex` could panic with `openssl: MD5 failed` while hashing filter-chain matches.

> - Change: The `ambex` component of Emissary-ingress now uses `xxhash64` instead of `md5`, since
>   `md5` can cause problems in crypto-restricted environments (e.g. FIPS) ([Remove usage of md5])
> [Remove usage of md5]: https://github.com/emissary-ingress/emissary/pull/5794

https://github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

## Enhancements (1)

- `EndpointSlice` support for Service endpoint resolution

## Dependency updates (3)

3 more, none mentioning security

- `- Feature: This upgrades Emissary-ingress to be built on Envoy v1.28.0 which provides security, performance and feature enhancements. You can read more about them here: <a href="https://www.envoyproxy.io/docs/envoy/v1.28.0/version_history/version_history">Envoy Proxy 1.28.0 Release Notes</a>`
- `- Change: Upgraded Emissary-ingress to the latest release of Golang as part of our general dependency upgrade process.`
- `- Change: Upgraded Emissary-ingress to the latest release of Golang as part of our general dependency upgrade process.`

## Other changes (5)

- Published YAML manifests no longer install the Ambassador Agent by default
- Regex-header `Mapping` cache keys now use `Mapping` names
- Regex-header `Mapping` cache keys use the Mapping name
- Emissary-ingress built on Envoy v1.28.0
- Client TLS details passed to external auth service

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
