emissary-ingress/emissary v4.0.0-rc.2

Emissary-ingress v4.0.0-rc.2

on GitHub

🎉 Emissary v4.0.0-rc.2 🎉

Emissary-ingress is an open source, Kubernetes-native microservices API gateway built on the Envoy Proxy.

Get started with Emissary-ingress - https://emissary-ingress.dev/docs/v4.0.0-rc.2/quick-start/
View changelog - https://github.com/emissary-ingress/emissary/blob/v4.0.0-rc.2/CHANGELOG.md

Quickstart

Emissary v4 supports both AMD64 and ARM64 architectures. To install Emissary v4 using Helm, follow the instructions in the Emissary Quickstart.

Emissary provides two Helm charts:

• ghcr.io/emissary-ingress/emissary-crds-chart is the chart for Emissary's CRDs.

• ghcr.io/emissary-ingress/emissary-ingress is the chart for Emissary itself.

The Emissary project recommends using Helm to install Emissary. If you need YAML instead, use helm template to generate the YAML manifests from the Helm charts.

Breaking Changes since v4.0.0-rc.1

• BREAKING CHANGE: Support for the extra metrics endpoint (set by supplying --metrics-endpoint on the command line for diagd) has been removed. This was a holdover from Ambassador Edge Stack (thanks to Jeremy Dinsel for the report!)

• BREAKING CHANGE: The default --banner-endpoint argument has been removed, since it was a holdover from Ambassador Edge Stack. If you want to use the diagnostics-banner functionality, you can now set AMBASSADOR_DIAGD_BANNER_ENDPOINT in the environment to the URL from which to fetch the banner.

Changes since v4.0.0-rc.1

• Fix: The diagnostics UI refers to Emissary (instead of Ambassador) and links to emissary-ingress.dev's docs.

• Fix: Emissary now uses the current string_match Envoy HeaderMatcher stanza rather than the deprecated exact_match stanza.

• Fix: Update many dependencies and the Python interpreter to resolve CVEs (thanks, Bhargav Joshi!).