RATATOSK
← All releases

Emissary-Ingressv3.10.0

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

Get Emissary-Ingress alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Upgrade guide1
Quickstart for fresh installs and upgrades
    See the [Quickstart](https://emissary-ingress.dev/docs/3.10/quick-start/) for more details.
github.com/emissary-ingress/emissary/releases/tag/v3.10.0

Breaking changes2

Published YAML manifests no longer install the Ambassador Agent by default

AffectsEmissary-ingress installations from published YAML manifests

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

Show release-note lines
- 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>.
github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

Emissary image and Helm charts listed at GHCR

AffectsEmissary 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.

Show release-note lines
- 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`
github.com/emissary-ingress/emissary/releases/tag/v3.10.0

Important fixes1

  • MD5 panic in ambex route hashing fixed
    AffectsEmissary 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
    github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

Enhancements1

Dependency updates3

    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 changes5
    • Published YAML manifests no longer install the Ambassador Agent by default
      - Change: Emissary-ingress will no longer publish YAML manifests with the Ambassador Agent being
        installed by default.
      github.com/emissary-ingress/emissary/releases/tag/v3.10.0
    • Regex-header Mapping cache keys now use Mapping names
      - Bugfix: Emissary-ingress was incorrectly caching Mappings with regex headers using the header name
        instead of the Mapping name, which could reduce the cache's effectiveness. This has been fixed so
        that the correct key is used. ([Incorrect Cache Key for Mapping])
      github.com/emissary-ingress/emissary/releases/tag/v3.10.0
    • Regex-header Mapping cache keys use the Mapping name
      - Bugfix: Emissary-ingress was incorrectly caching Mappings with regex headers using the header name
        instead of the Mapping name, which could reduce the cache's effectiveness. This has been fixed so
        that the correct key is used. ([Incorrect Cache Key for Mapping])
      [Incorrect Cache Key for Mapping]: https://github.com/emissary-ingress/emissary/issues/5714
      - Bugfix: Emissary-ingress was incorrectly caching Mappings with regex headers using the header name
        instead of the Mapping name, which could reduce the cache's effectiveness. This has been fixed so
        that the correct key is used. ([Incorrect Cache Key for Mapping])
      [Incorrect Cache Key for Mapping]: https://github.com/emissary-ingress/emissary/issues/5714
      github.com/emissary-ingress/emissary/releases/tag/v3.10.0
    • Emissary-ingress built on Envoy v1.28.0
      - 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>
      github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md
    • Client TLS details passed to external auth service
      - Feature: Emissary-ingress now passes the client TLS certificate and SNI, if any, to the external
        auth service. These are available in the `source.certificate` and `tls_session.sni` fields, as
        described in the <a
        href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/auth/v3/attribute_context.proto">
        Envoy extauth documentation</a>.
      github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

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