Yandex Application Load Balancer release notes
Q3 2026
-
Extended support for mutual TLS (mTLS) authentication. For inbound client TLS certificates, added the
accept_untrustedsetting for accepting without trust chain verification and theallow_expiredsetting for accepting expired certificates. For outbound connections to backends and health checks, Application Load Balancer can use a client certificate from Certificate Manager.These settings are available via the API, CLI and Terraform.
-
For target resources, added the ability to explicitly specify an availability zone in the
localityfield. The availability zone is used for traffic localization. This setting is available via the API. -
Added host description (the
descriptionfield) to Audit Trails events about creating, updating, and deleting virtual hosts. -
Added automatic processing of incomplete operations that could previously require a manual restart after failure or a timeout.
-
Added the check of the internal IPv4 listener subnet: it must belong to the load balancer network. An incorrect configuration is rejected before the operation starts.
-
Fixed bugs related to:
- Managing links to certificates used for mTLS.
- Applying approved exceptions from the listener number limit when creating a load balancer.
- Action menu position in resource cards in the management console.
Q2 2026
-
Added the ability to preserve the case of HTTP header names for HTTP/1.1 using the
preserve_http1_header_casingsetting. This setting is specified for a specific listener and helps you with applications that are case-sensitive to header names.This setting is available via the API, CLI, and Terraform.
-
Added
labelsanddescriptionfor virtual hosts. This setting is available via the API. -
Added sending of Audit Trails events about virtual host updates due to HTTP router updates. Changes in hosts are now recorded when they are updated within a router too.
-
Made the PEM
format validation of trusted CA certificates stricter: invalid certificates are rejected before applying the load balancer configuration. -
In the management console, added the ability to add load balancers, HTTP routers, backend groups, and target groups to favorites.
-
Accelerated the completion of operations when configuring a load balancer.
-
Fixed the following errors in the management console:
- When cyrillic characters are saved in the body of a direct HTTP response when configuring an HTTP router.
- When Global RateLimit limitations are linked to routes when sorting, updating, or disabling limitations.
- When redirect HTTP codes are displayed in the HTTP router configuration form.
Q1 2026
-
Added the support for mutual TLS (mTLS) authentication between the client and load balancer HTTPS listener. To verify client certificates, specify a root CA certificate in PEM
format. You can provide the client certificate as well as information about its issuer and subject to the backend in HTTP headers for client identification and audit.This setting is available via the API and CLI. See the configuration procedure in Terminating TLS connections.
-
Extended sending of Audit Trails events for virtual hosts. Events are sent on host operations via the HTTP router as well as on creating or deleting hosts together with the router.
-
Fixed bugs related to:
- When a link to a connected Smart Web Security security profile was deleted when updating other virtual host fields via the API with
update_mask. - When displaying target group VMs in the management console with matching IP addresses in different subnets.
- When a link to a connected Smart Web Security security profile was deleted when updating other virtual host fields via the API with
Q4 2025
-
In the management console
, now you can start a zonal shift for one or more availability zones, as well as schedule a time to automatically cancel the shift. -
Added request path support for cookie-based session affinity. This ensures correct session merges for specific sections of your website or web app.
Q3 2025
-
Added the ability to manually disable one or more availability zones in the event of local issues or to test the load redistribution mechanism. You can also specify the availability zone off time. After this time runs out, the availability zone will be automatically re-enabled.
This feature is available through the Yandex Cloud CLI and API.
-
Now, you can allow or deny auto-disabling an availability zone. The auto-disabling is performed by Yandex Cloud staff if an availability zone is under maintenance or shows signs of failure.
This feature is available through the Yandex Cloud CLI, Terraform, and API.
-
Added support for modification of HTTP request parameters for specific routes on a virtual host. This feature may be of use for managing API versions, microservice routing, backward compatibility, and URL normalization.
The
path-regex-rewritemodification parameter was added to the following route management commands:append-http-route,prepend-http-route,insert-http-route, andupdate-http-route.This feature is available through the Yandex Cloud CLI, Terraform, and API.
-
You can now deactivate the use of a Smart Web Security security profile to check traffic on a specific virtual host route. This can be of use when, on some routes, requests come from trusted sources and need not be analyzed.
The
disable-security-profileparameter was added to route managing commands.This feature is available through the Yandex Cloud CLI, Terraform, and API.
Q4 2024
-
Added the Global RateLimit module to limit HTTP and gRPC requests per virtual host. The limit can be applied to the entire virtual host or individual routes.
This feature is currently in preview. To enable it, contact support
. -
Added support for custom HTTP status codes as valid responses for backend health checks. Code values can range from 100 to 599.
-
Added an option of keeping a connection alive even if the health check fails. This option is only available for Stream health checks.
-
Added configurable idle timeout settings for Stream and SNI listeners.
-
Added a description for the x_forwarded_for field in load balancer logs.
All new features are now available through CLI, API, and Terraform interfaces.
Q2 2024
- Added validation for internal IPv4 addresses during load balancer creation and updates.
- Fixed the validation issue causing mixing weighted and non-weighted backends in target groups during their creation and updates.
Q1 2024
- Improved data plane stability for more reliable service data processing and transmission.
- Implemented integration with Yandex Smart Web Security:
- Associating virtual hosts with security profiles using the management console, CLI, Terraform, or API.
- Smart Web Security event log forwarding to theYandex Cloud Logging log group.
- Smart Web Security metric forwarding to Yandex Monitoring.
- Changed behavior for
Streambackend groups: The load balancer now terminates connections to backends that fail health checks. - Optimized work with the service resource operation list.
- Added support for searching load balancers by internal IP address in the management console.
- Added granular availability zone selection for load balancer nodes in the management console.
- Resolved validation errors when changing load balancer listener types between
TLSandStreamin the Terraform provider.