gateway
gateway copied to clipboard
envoyproxy
Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway
*Description*: >Describe the desired behavior, what scenario it enables and how it would be used. Similar to patching the envoy deployment (implemented in https://github.com/envoyproxy/gateway/pull/2374) also support patching envoy service
*Description*: This issue tracks the performance (Throughput, Latency) of Envoy Gateway control plane and data plane at scale (Service, xRoutes, Gateway, Client Connections) . * The output of this issue...
*Description*: >Describe the desired behavior, what scenario it enables and how it would be used. Relates to https://github.com/envoyproxy/gateway/pull/2053 & https://github.com/envoyproxy/gateway/issues/1821 [optional *Relevant Links*:] >Any extra documentation required to understand the...
*Description*: >Describe the desired behavior, what scenario it enables and how it would be used. https://github.com/envoyproxy/gateway/pull/2374 added support for supporting patching the envoy deployment. Errors can be handled better by...
If 2 backend pods are undergoing a rolling restart, add outlier detection and retry settings in Envoy proxy to ensure no traffic intended for the backend is dropped
Upgrades
*Description*: - [ ] #1711 - [x] #1712 - [x] #1713 - [x] #1743 [optional *Relevant Links*:] >Any extra documentation required to understand the issue.
*Description*: >Describe the issue. The steps to upgrade Envoy Gateway is different than when installing Envoy Gateway for the first time. Since helm skips updating the CRDs, we need to...
*Description*: ```yaml apiVersion: gateway.networking.k8s.io/v1beta1 kind: Gateway metadata: name: infra-gateway spec: gatewayClassName: infra-gateway listeners: - name: grpc-https hostname: 'grpc.example.com' protocol: HTTPS port: 443 allowedRoutes: namespaces: from: Same tls: certificateRefs: - group:...
Metadata
Owner
Metadata
Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway