Daneyon Hansen

Currently: `fgrpc.PingServer(*grpcPortFlag, fgrpc.DefaultHealthServiceName)` If/when #204 gets merged: `fgrpc.PingServer(*grpcPortFlag, *serverCertFlag, *serverKeyFlag, fgrpc.DefaultHealthServiceName)`

Adds Envoy Deployment Support

1

Adds initial Envoy deployment support to Infra Manager. Fixes: #185 Signed-off-by: danehans

Should we add gatewayapi/helpers.go to coverpkg?

1

Do we want to add `gatewayapi/helpers.go` to `-coverpkg=./...` so that it doesn't matter which package the tests belong to when counting coverage? xref: https://github.com/envoyproxy/gateway/pull/196#issuecomment-1211092656

Docs Publishing Strategy

15

Should Envoy Gateway's documentation be separate from Envoy's [official docs](https://www.envoyproxy.io/docs/envoy/latest/) or integrate with https://github.com/envoyproxy/envoy-website

Update Community Meeting Time

1

The community meeting currently has the following issues: 1. Is longer than most OSS meetings. 2. Overlaps every other week with the GAMMA community call. 3. Is not friendly for...

Add Gateway Status Support

3

*Description*: Add initial support for gateway status. Depends on: https://github.com/envoyproxy/gateway/pull/150 https://github.com/envoyproxy/gateway/pull/164 [optional *Relevant Links*:] The implementation should follow [Contour's implementation](https://github.com/projectcontour/contour/blob/main/internal/status/gatewaystatus.go), and be consistent with the existing Kube provider [controllers](https://github.com/envoyproxy/gateway/tree/main/pkg/provider/kubernetes).

Create Compatibility Matrix

7

A matrix is needed that describes component versions used in EG releases. For example, EG v0.1 = Envoy v1.x, Gateway API v1.y, etc.

Finalize License Header Management

6

Kubernetes and many other projects include a license header in each project code file while Envoy only requires license headers at the project root. With https://github.com/envoyproxy/gateway/pull/84, EG will follow the...

Provide a Simple and Native Certificate Management Solution

1

While https://github.com/envoyproxy/gateway/issues/81 identifies the need for a production-quality certificate management solution, EG should support native cert management for simple, non-prod use cases.

https://github.com/envoyproxy/gateway/pull/16 specifies the need for a Config Server (CS) component to allow EG to be configured from a remote endpoint. The CS details should be captured in this issue or...