You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HTTP Filters can be applied to a specific xDS Cluster using the http_filters field .
Can the Dynamic Forward Proxy HTTP Filter be supported as an upstream filter ?
[optional Relevant Links:]
Any extra documentation required to understand the issue.
The text was updated successfully, but these errors were encountered:
I would ideally like to model the Dynamic Forward Proxy feature as an input Backend resource in Envoy Gateway. This Backend resource has a 1:1 mapping with an xDS Cluster. So by representing Dynamic Forward Proxy as a Backend Resource (for the end user, its a Backend of type ForwardProxy that discovers endpoints based off DNS of the Host header), I can scope all the xDS configuration (dynamic forward proxy http_filter + special cluster type ) to the xDS Cluster, so only requests meant for this backend executes this filter + cluster, instead of all requests hitting the listener (above example in envoy docs has the filter defined in the hcm)
Description:
HTTP Filters can be applied to a specific xDS Cluster using the http_filters field .
Can the Dynamic Forward Proxy HTTP Filter be supported as an upstream filter ?
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: