Docsright arrowEmissary-ingressright arrowMajor Changes in Emissary-ingress 3.X

2 min • read

Major Changes in Emissary-ingress 3.X

The 3.X family introduces a number of changes to ensure Emissary-ingress keeps up with latest Envoy versions and to support new features such as HTTP/3. We welcome feedback! Join us on Slack and let us know what you think.

Emissary-ingress 3 is functionally compatible with Emissary-ingress 2.x, but with any major upgrade there are some changes to consider. Such as, Envoy removing support for V2 Transport Protocol features. Below we will outline some of these changes and things to consider when upgrading.

1. Envoy Upgraded to 1.22

Emissary-ingress 3.X has been upgraded from Envoy 1.17.X to Envoy 1.22 which keeps Emissary-ingress up-to-date with the latest security fixes, bug fixes, performance improvements and feature enhancements provided by Envoy Proxy. Most of the changes are under the hood but the most notable change to developers is the removal of support for Envoy V2 Transport Protocol. This means all AuthServices and LogServices must be updated to use the V3 Protocol.

This also means some of the v2 runtime bootstrap flags have been removed as well:

2. Envoy V2 Protocol Support Removed

With the upgrade to Envoy 1.22, the V2 Envoy Transport Protocol is no longer supported. Emissary-ingress 3.X only supports V3 Envoy API.