Arko Dasgupta

trying to summarize this discussion regarding docs, please correct me if im wrong * Envoy Gateway will use its own doc publishing pipeline to generate html content. * This content...

thanks for sharing the details @phlax ! so my takeaway is - Envoy Gateway will need a CI workflow similar to what [Envoy has](https://github.com/envoyproxy/envoy/blob/main/docs/publish.sh) when it wants to publish html...

thanks for raising this @youngnick . would like to wait for some more guidance from CNCF https://github.com/cncf/tag-security/issues/895 before making a decision especially for Container Image SBOM. I see a lot...

will create an epic for each component once https://github.com/envoyproxy/gateway/pull/16 is merged :)

hey @danehans I plan on working on this

busy with other issues, unassigned myself for now, in case someone wants to pick this one up

linking https://github.com/tetratelabs/func-e/issues/433 here which should allow downstream projects like this one to programmatically run envoy which can be used for xds server end to end testing

fixed with https://github.com/envoyproxy/gateway/pull/425

hi @thomasrockhu-codecov, answering on behalf of @ethanhanjiahao, it does, and its [here](https://github.com/envoyproxy/gateway/blob/main/.github/codecov.yml), yet we saw in [this PR ](https://github.com/envoyproxy/gateway/pull/728#discussion_r1042709751)that a drop in the coverage below threshold didn't fail the CI

thanks for finding this bug @nipsufn should we instead be defining the deployment port here https://github.com/envoyproxy/gateway/blob/72fadb7c1dbe7d660c2900527c34f53cfcfce7ac/charts/gateway-helm/values.tmpl.yaml#L15 ? cc @Xunzhuo