Lior Okman
Lior Okman
> more work is required to build a better API contract for this feature and improve the API Agreed. My intent was to update the [PostHTTPListenerExtensionContext](https://github.com/liorokman/gateway/blob/main/proto/extension/context.proto#L35C9-L35C41) so that it would...
If not the `ClientTrafficPolicy`, then I think a new policy type is needed here to support the `vendor`/`extension developer` persona. The `EnvoyGateway` resource seems wrong because there might be a...
The biggest difference between using the ExtensionManager and maintaining sets of EnvoyPatchPolicy documents is that JSON patches are hard to get right, and when they stop applying cleanly due to...
What I would like to have is the ability to attach some resource(s) in Kubernetes that to a listener, such that when the extension server's `PostHTTPListenerHook` is called for that...
> * Sending specific context for specific gateway api resources - can 3. be solved using a `selector` / `match` structure that supports label selectors, which looks something like this...
>This API proposes to send different resources to different Gateway/Listeners. Is this level of flexibility needed? If one `Gateway` belongs to one application and another `Gateway` belongs to a different...
> @kflynn mentioned this GEP: https://gateway-api.sigs.k8s.io/geps/gep-1867 in a different discussion. @liorokman - do you think that GW parameters can be used here as an alternative (acting like HTTPRoute filters) ?...
> another point I'm hoping we an discuss here, have we ruled out the ability to infer context from a extension CRD using > Spec.TargetRef or Spec.TargetRefs field that maps...
> I’m concerned about the complexity involved in implementing the ExtensionContextPolicy. While the ExtensionContextPolicy is linked to a Gateway API Custom Resource (CR), it is the extension server’s responsibility to...
I think that `ClientTrafficPolicy` only affects `HTTPRoutes` and `GRPCRoutes`. There's a comment in the code that says that supporting `ClientTrafficPolicy` for TCP and TLS routes required #1635 to be merged...