Arko Dasgupta

I think we should support last 5 k8s versions, similar to what upstream Gateway API supports but we could reduce CI time, and only run 1st, 3rd and 5th k8s...

@MregXN this is not supported, highlighted in https://gateway.envoyproxy.io/latest/user/gatewayapi-support/#httproute keeping this issue open to we can highlight this using a status condition

@MregXN can you share your use case of why you'd prefer enabling the filter on the backendRef instead of the route

@MregXN by forwarding operations, do you mean appending headers to the request or response ?

I miscalculated the effort to get this in :( The implementation seems straightforward 1. Add new filter related fields in the [DestinationSetting](https://github.com/envoyproxy/gateway/blob/0d1ebfd8aafde624ef3290c1fd83b237e93459d9/internal/ir/xds.go#L864) IR similar to [this](https://github.com/envoyproxy/gateway/blob/0d1ebfd8aafde624ef3290c1fd83b237e93459d9/internal/ir/xds.go#L448) 2. Set them in...

@cnvergence planning on working on this one ?

relates to https://github.com/envoyproxy/gateway/pull/2405 @Xunzhuo is a knob to opt out of this translation the only option ?

@zvlb would be great if you can take #2405 forward (as a new PR) some open questions are * right home - should this field live inside [EnvoyGateway](https://github.com/envoyproxy/gateway/blob/9a626f262317b90946219d7f85069221cce2c4b6/api/v1alpha1/envoygateway_types.go#L194) config or...

@zesiar0 can you comment here so we can assign this to you ?

this makes a lot of sense cc @mt-inside @zhaohuabing @missBerg 2 open questions * do we need to revisit the `prefix` naming here ? * should this be a prefix,...