Guy Daich

### Version _No response_ ### Is your feature request related to a problem? Please describe. Currently, envoy retries are fired in [0, 250]ms [intervals](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/router_filter#config-http-filters-router-x-envoy-max-retries). By exposing the retry policy [backoff...

### Version 1.10.x (latest stable) ### Is your feature request related to a problem? Please describe. Gloo Edge and Federation Control Planes (Gloo, Gateway, Gloo-Fed ... ) should support HA...

Publish Charts with Image Digests

8

### Version 1.11.x (latest stable) ### Is your feature request related to a problem? Please describe. Pulling images by digest can be beneficial: [[1]](https://cloud.google.com/architecture/using-container-image-digests-in-kubernetes-manifests), [[2]](https://blog.aquasec.com/docker-image-tags). ### Describe the solution you'd...

Canary Deployments with Gloo Federation

7

### Version 1.11.* ### Is your feature request related to a problem? Please describe. Gloo Edge supports in-place canary deployment: multiple control planes can reconcile the same CRs and produce...

Support listener access logging

5

### Version 1.14.x (latest stable) ### Is your feature request related to a problem? Please describe. Downstream connections that fail to be established are not reported in the HCM or...

api: connection limits

1

**What this PR does / why we need it**: Adds a container for connection-level settings to CTP called `Connection`. Currently, connection will only support the `Limit` attribute for setting the...

*Description*: Limiting active connections for an edge proxy is a security and resilience best practice, as described in the Envoy [edge best practices](https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge) document. When a single Envoy deployment is...

*Description*: >Describe the desired behavior, what scenario it enables and how it Relates to #2678 [optional *Relevant Links*:] >Any extra documentation required to understand the issue.

*Description*: >Describe the issue. Relates to https://github.com/envoyproxy/gateway/pull/2678 [optional *Relevant Links*:] >Any extra documentation required to understand the issue.

API: EnvoyExtensionPolicy

2

**What this PR does / why we need it**: This PR introduces a new policy type, `EnvoyExtensionPolicy`, that can be used by Gateway operators add multiple HTTP and Network extension...