gateway
gateway copied to clipboard
Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway
### *Description*: There's some unexpected Pod during this process for deleting gateways with `mergeGateways` features on. ### *Repro steps*: 1. Apply the manifest from [quickstart](https://gateway.envoyproxy.io/latest/user/quickstart/) 2. Apply these config below,...
*Description*: test details in https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/tests/gateway-static-addresses.yaml Once fixed, please enable in https://github.com/envoyproxy/gateway/blob/main/test/conformance/conformance_test.go & https://github.com/envoyproxy/gateway/blob/main/test/conformance/experimental_conformance_test.go Skipped in https://github.com/envoyproxy/gateway/pull/1987
**What type of PR is this?** fix **What this PR does / why we need it**: Like , I've encountered a case when converting the following ingress definition: ```yaml apiVersion:...
### What type of PR is this? feat(controller): implement leader election for EG controller ### What this PR does / why we need it: 1. This PR introduces leader election...
*Description*: >Describe the desired behavior, what scenario it enables and how it would be used. As a user, I would like to limit the client IP address to a few...
Add a overload manager configuration to limit the total number of downstream connections https://www.envoyproxy.io/docs/envoy/latest/configuration/operations/overload_manager/overload_manager#limiting-active-connections
*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...
**What type of PR is this?** **What this PR does / why we need it**: **Which issue(s) this PR fixes**: Fixes https://github.com/envoyproxy/gateway/issues/3364
*Description*: >Describe the issue. relates to https://github.com/envoyproxy/gateway/issues/2598 [optional *Relevant Links*:] >Any extra documentation required to understand the issue.
*Description*: >Describe the desired behavior, what scenario it enables and how it would be used. Users would like to route to a specific backend by matching on JWT claims Looks...