You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Limiting active connections for an edge proxy is a security and resilience best practice, as described in the Envoy edge best practices document.
When a single Envoy deployment is proxying multiple backends, it could be beneficial to apply granular downstream connection limits, e.g. per Gateway or Listener. This creates a degree of resource isolation between different backends exposed by the proxy and allows Envoy Gateway administrators to allocate resources based on the expected volume of traffic, SLAs, etc.
EG's Client Traffic Policy can be extended to support connection limits. The best candidate for implementation is the Envoy Network Connection Limit Filter.
The text was updated successfully, but these errors were encountered:
Description:
Limiting active connections for an edge proxy is a security and resilience best practice, as described in the Envoy edge best practices document.
When a single Envoy deployment is proxying multiple backends, it could be beneficial to apply granular downstream connection limits, e.g. per
Gateway
orListener
. This creates a degree of resource isolation between different backends exposed by the proxy and allows Envoy Gateway administrators to allocate resources based on the expected volume of traffic, SLAs, etc.Envoy can limit L4 connections in various levels:
EG's Client Traffic Policy can be extended to support connection limits. The best candidate for implementation is the Envoy Network Connection Limit Filter.
The text was updated successfully, but these errors were encountered: