[ ] Deploy EnvoyProxy Instance in Gateway CR namespace
[x] Deploy EnvoyProxy Instance in Envoy Gateway namespace
[x] Multi-tenancy Envoy Gateway in different namespace
[x] Multi Cluster Support with MCS API
Day 2 Operations
[x] Install
[x] Helm
[x] Yaml
[x] Observability
[x] Data Plane
[x] Control Plane
[x] egctl command line tool
[x] Core
[ ] Extended
[ ] Triage
[x] HPA
[x] Upgrades (CRD, Envoy Proxy, Envoy Gateway)
[x] Customize Envoy Kubernetes Resources
Documentation
[ ] Document all features, operations, and other relevant information
Other
Team Session
All issues related to GA should be managed under Envoy Gateway: The Road to GA, which includes the following sections: Backlog, Todo, In Progress, Review, and Done.
All issues related to GA should be labeled for identification: road-to-ga
Blog Post
[x] Publish a blog post about Envoy Gateway on both blog.envoyproxy.io and gateway.envoyproxy.io
Envoy Gateway GA Plan
This issue tracks all the necessary steps for Envoy Gateway to reach
v1.0
, providing users with the confidence to run it in production.Plan Release Time: The GA is planned for early March 2024, before KubeCon Paris 2024.
Stability
Performance at Scale
API Gateway Features
Core (Gateway API Implementation)
Implement and expose the majority of API Gateway features using a stable API. This requires the upstream Gateway APIs to be graduated (tracked with https://github.com/kubernetes-sigs/gateway-api/discussions/1801)
Protocol Support
Cross Namespace Access Control
Traffic Management
Extended (Envoy Gateway Policy Attachment)
Security
Traffic Management
Client Side
Backend Side
Extensibility
Flexible Deploy Mode
Day 2 Operations
egctl
command line toolDocumentation
Other
Team Session
road-to-ga
Blog Post
CNCF Logo Design