Envoy Gateway GA Plan

[Xunzhuo]

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.

I will be responsible for: manage GitHub issue/project, set priorities, and release the v1.0.0.

Stability

• Pass conformance tests for all v1.0 Gateway API upstream features
• Write and pass E2E tests for all extended features
• Achieve 60%-80% code coverage (from unit tests)

Performance at Scale

• Meet certain performance criteria when used at scale
• Performance Report

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 kubernetes-sigs/gateway-api#1801)

Protocol Support

• HTTP
• gRPC
• TCP
• TLS
• UDP

Cross Namespace Access Control

• ReferenceGrant

Traffic Management

• More Advanced Match Routing Rules:
  • Header
  • Method
  • Param
  • Host
  • Path
• Timeout
• Request Header Modifier
• Response Header Modifier
• Request Mirror
• Request Redirect
• URL Rewrite
• Weighted Backend

Extended (Envoy Gateway Policy Attachment)

Security

• CORS
• BasicAuth
• JWT
• OIDC

Traffic Management

Client Side

• EnableProxyProtocol
• TCPKeepAlive
• HTTP3/QUIC

Backend Side

• Global Ratelimit
• Local Ratelimit
• LoadBalancing
• ProxyProtocol
• TCPKeepAlive
• Active Health Check
• Retry
• Circuit Breaker
• Fault Injection

Extensibility

• Envoy Gateway Extension Manager
• EnvoyPatchPolicy
• WASM/Go/Lua PluginPolicy

Flexible Deploy Mode

• Multiple GatewayClass per Envoy Gateway
• One GatewayClass per Envoy Gateway
• Merged Gateway per Envoy Gateway
• Namespaces scope watch mode
• Cluster scope watch mode
• Deploy EnvoyProxy Instance in Gateway CR namespace
• Deploy EnvoyProxy Instance in Envoy Gateway namespace
• Multi-tenancy Envoy Gateway in different namespace
• Multi Cluster Support with MCS API

Day 2 Operations

• Install
  • Helm
  • Yaml
• Observability
  • Data Plane
  • Control Plane
• egctl command line tool
  • Core
  • Extended
• Triage
• HPA
• Upgrades (CRD, Envoy Proxy, Envoy Gateway)
• Customize Envoy Kubernetes Resources

Documentation

• Document all features, operations, and other relevant information

Other

Team Session

1. 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.
2. All issues related to GA should be labeled for identification: road-to-ga

Blog Post

• Publish a blog post about Envoy Gateway on both blog.envoyproxy.io and gateway.envoyproxy.io

CNCF Logo Design

• Design a CNCF logo for Envoy Gateway