Arko Dasgupta

should these live in `Backend` instead ?

+1 if this can be solved by adding a type in the Backend resource called Original Destination / `StaticResolver`, it has the same security implications as the `DynamicResolver` / Dynamic...

cc @Jeffwan @varungup90

instead of using Original Destination Cluster, this can also be represented as a LoadBalancer field in BTP https://gateway.envoyproxy.io/docs/api/extension_types/#loadbalancer which uses the new Envoy Override Host Load Balancer Policy https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/load_balancing_policies/override_host/v3/override_host.proto which...

The BTP can attach to the Gateway or Route. Is the BackendRef / Service definition static/known before hand so the IP in the header must be an endpoint of the...

pods having the same label can be represented by a service using the label as a selector https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service so the [InferencePool](https://gateway-api-inference-extension.sigs.k8s.io/reference/spec/#inferencepoolspec) could be represented as a Service by the EG...

refining my prev comment, outlining the 2 options in detail here (names and API fields are temporary) Option 1 - Representing this as a `LoadBalancer` config in `BackendTrafficPolicy` where the...

thanks @wbpcode, that should make the API simpler to ``` staticResolver: from: header: "x-endpoint-ips" ```

will it be better to define a `bool` field that says `clientIdInSecret` ?

thanks @zirain ! quick q - how this is impact our release process cc @guydc @Xunzhuo