Replies: 1 comment 1 reply
-
In general, Policy objects are implementation specific, and that includes the ClientSettingsPolicy, so it's expected that that config would not work when used with a GatewayClass that's not implemented by Nginx Gateway Fabric. It seems like the feature you are really looking for is being able to limit the size of a response body and being able to use that with other implementations? I don't think we've had a direct request for that before, so some more detail on why you would like that would be great. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm running Gateway API v1.1.0 & Nginx Gateway Fabric v1.3.0. I'm following this example- https://docs.nginx.com/nginx-gateway-fabric/how-to/traffic-management/client-settings/ to test it out.
Gateway.yaml & Client Setting Policy.yaml
I don't see any status /Accepted for the clientsettingspolicies.gateway.nginx.org. Started this thread nginxinc/nginx-gateway-fabric#2306 and got NGF implementation using
GatewayClass: Nginx
. Can we implement it without this nginx GatewayClass native to gateway.networking.k8s.io CRD's ?Beta Was this translation helpful? Give feedback.
All reactions