Create Compatibility Matrix
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.
Based on our Contour experiences, I'd suggest we make a simple JSON or YAML file that we can generate the matrix from to start with. Ideally, we should be able to do some SBOM things, and that should have all the info needed, btu that will take some time.
Items to doc:
- Envoy version
- Gateway API version
- Kube version(s0 (for Kube provider).
The above should be based on the versions used/tested by EG.
@flynn has volunteered to take this on. @lizan @mattklein123 @phlax I'm unable to assign @flynn.
xref #17
I think we should pin envoy to a specific image to be more deterministic by changing https://github.com/envoyproxy/gateway/blob/62bfc55332b0d1e47fad4f77e40713f3e52cb0b8/internal/ir/infra.go#L14 @lizan any advice on which version https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history should we pick for v0.2.0 ?
The Gateway API version currently being used in v0.5.0 https://github.com/envoyproxy/gateway/blob/62bfc55332b0d1e47fad4f77e40713f3e52cb0b8/go.mod#L20
Let's use envoyproxy/proxy:v1.23.1, or envoyproxy/proxy:v1.23-latest.