enterprise-2.18.3
July 29, 2025
The 2.18.3 stable point release includes bugfixes and minor improvements.
Previous release: enterprise-2.18.2.
Supported Kubernetes versions
For this release, the minimum supported Kubernetes version remains 1.22, and the maximum supported Kubernetes version remains 1.32.
Who should upgrade?
We recommend that all customers using BEL 2.18.0–2.18.2 upgrade to 2.18.3 as soon as possible to take advantage of the stability fixes and increased resiliency in this release. All other customers should upgrade at their convenience.
Upgrade guidance
This is a stable point release designed to introduce minimal change. Please see the instructions in Upgrading BEL for how to upgrade.
To upgrade with BEL’s lifecycle automation operator, you will need Buoyant Extension version v0.36.0 or later.
Changelog
- Fix a bug where upgrading to 2.18.x from pre-2.18 versions causes duplicate proxy metrics (linkerd2-proxy#3987)
- Increase proxy connection retry maximum backoff durations (linkerd2-proxy#3992)
- Skip invalid Server resources by logging the skipped Server and continuing with other valid Servers (linkerd2#14195)
- Fix a bug that caused increased proxy connection pool sizes and memory utilization for HTTP/1 clients communicating with many virtual hosts (linkerd2-proxy#4004)
- Implement a lower default limit of 10K outbound idle connections per-host (linkerd2-proxy#4005)
- Implement a lower default limit of 10K inbound connections per-workload (linkerd2-proxy#4007)
- Fix a bug that caused metadata about installed extensions to transit over the default TLS crypto stack in FIPS-enabled environments