enterprise-2.19.4
December 19, 2025
The 2.19.4 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.
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
Important: If you are a FIPS user and are upgrading from BEL 2.18, in order to preserve zero-downtime upgrades, you must first upgrade to 2.18.7 before upgrading to this release.
(For clarity, non-FIPS users who are upgrading from BEL 2.18 may upgrade as usual without this restriction, i.e. even from releases prior to 2.18.7; and FIPS users who are on running an earlier BEL 2.19 release may also upgrade as usual.)
Those caveats aside, 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.1 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