edge-25.3.2
Breaking Changes📦 linkerdView on GitHub →
⚠ 2 breaking✨ 1 features🐛 3 fixes🔧 4 symbols
Summary
This release changes the default for `outbound-transport-mode` to `transport-header` and fixes an issue with Helm installing Gateway API CRDs incorrectly. It is strongly recommended to use edge-25.7.4 instead due to known issues, including lack of IPv6 support.
⚠️ Breaking Changes
- The default for `outbound-transport-mode` is now `transport-header`. This means all traffic between meshed proxies flows over port 4143 instead of the original destination port, which might break clients expecting traffic on the original port.
- If a client closes a connection without writing any data, the protocol detection proxy treats this as a read failure. Clients using unusual half-open connections might see behavioral changes; such clients may need to have their connections marked as opaque.
Migration Steps
- If you have clients that rely on connections being open without data being sent (half-open connections), consider marking those connections as opaque due to changes in protocol detection behavior.
- Review configurations if relying on inter-proxy traffic using original destination ports, as the default `outbound-transport-mode` is now `transport-header` (using port 4143).
✨ New Features
- Inbound server metrics now include a `srv_port` label to identify the specific port used for inbound policy.
🐛 Bug Fixes
- Fixed a bug where installing with Helm could install Gateway API CRDs even when `enableHttpRoutes`, `enableTcpRoutes`, or `enableTlsRoutes` were set to false.
- Improved metrics around protocol declarations and protocol detection, especially when using the `transport-header` mode.
- Admin traffic is no longer sent over opaque transport.
🔧 Affected Symbols
protocol detection proxyoutbound-transport-modeGateway API CRDsinbound server metrics