Arko Dasgupta

@skriss what about the other status conditions (within the Gateway and HTTPRoute) set by the translator in the first iteration but have changed in the second iteration (due to change...

> Yeah you may have similar issues for those. I'd say clearing the existing conditions before translate is probably a good first step, but yeah ultimately we probably need more...

I prefer option 4 - Add global library logging scopes This simplifies enabling component level logging and is also used in istio (here's an [example](https://github.com/istio/istio/blob/247e396dd30635ba44e81f324f4224967b75e02a/pkg/webhooks/validation/controller/controller.go#L51)) More info on this is...

Here's one way to do it * Lets try and implement Global Ratelimiting directly using xDS * Lets define a new CRD called EnvoyPatch which can be used to represent...

sure, this might not be part of the first release but since this is highlighted in the [goals](https://github.com/envoyproxy/gateway/blob/main/GOALS.md#extensibility), im kickstarting the discussions, since it might require [upstream](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#api-specification) API changes.

cool, sg, should we start off with the same approach - all official EG or all BYO, for [Bootstrap](https://www.envoyproxy.io/docs/envoy/latest/api-v3/bootstrap/bootstrap) as well ?

hey @zirain what about port forwarding to the envoy pod ?

I understand your pain :). I think we might have to continue with above workflow until * we have a debug subcommand such as `envoy-gateway collect` to collect `config_dump` and...

thanks for addressing the comments ! the xds config looks good, have some minor suggestions, mainly to simplify the life of the dev adding TCPRoute support, but not blockers. @skriss...

@chauhanshubham when possible can you also attach a working example, there doesnt seem to be an existing conformance test for TLS passthrough yet