enterprise-2.18.7
December 15, 2025
The 2.18.7 point release fixes an issue with TLS algorithm negotiation that may affect connection establishment with other FIPS proxy versions. It also reduces memory consumption in the destination controller when running federated services with large-scale rollouts.
Previous release: enterprise-2.18.5.
(Note that there is no enterprise-2.18.6 release.)
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?
Users who run the FIPS-validated version of BEL should upgrade to this release when feasible.
Users of federated services who experience excessive memory usage in the destination controller during large-scale rollouts should upgrade to this release when feasible.
Other users should upgrade to this release 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.38.0 or later.
Changelog
- Fix an issue with TLS algorithm negotiation that may affect connection establishment with other FIPS-validated proxy versions
- Fix an issue in the destination controller when running multi-cluster federated services that may cause an increase in memory consumption
- Update
golangto remediate CVE-2025-61727 and CVE-2025-61729