Replies: 1 comment 2 replies
-
Thanks for the feedback @jancorluy! Our approach to this will be twofold. One is to provide a mechanism to add directives to the NGINX configuration much like the Ingress annotations via "snippets" before. The other is to promote more popular use cases to first-class abstractions using extensions of the Gateway API. Proxy buffer configuration just so happens to be one of those first-class abstractions we had planned in its own ProxySettingsPolicy. We also have an issue to track this as well, pinned for 2.0 (after 1.4) at the moment, which is at least four months off. The NGINX customization feature should be coming then as well, so that will open NGF up to all of those settings without the first-class extensions. I can talk to the team about moving this one up to 1.4, but we might be pretty full there. I'll update this thread when I do! |
Beta Was this translation helpful? Give feedback.
-
In our company we have a few apps where we need to be able to configure the proxy settings. This app is putting headers on a response and the size of these are to big, check this article:
https://medium.com/@christopherlenard/identity-server-and-nginx-ingress-controller-in-kubernetes-7146c22a2466
With nginx ingress controller we had the option to configure this by adding annotations on the ingress, now we don't have this option anymore while using nginx gateway.
I saw you are implementing ClientSettingsPolicy, which is a nice replacement and abstraction for the ingress class annotations, but unfortunatly I am unable to provide the proxy settings.
Let me know your toughts on this, because for us this is a crutial path to host Duende IdentityServer inside Kubernetes.
Beta Was this translation helpful? Give feedback.
All reactions