-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Filters in BackendRefs #2572
Comments
@MregXN this is not supported, highlighted in https://gateway.envoyproxy.io/latest/user/gatewayapi-support/#httproute |
I think I can help in making this issue achievable. |
@MregXN can you share your use case of why you'd prefer enabling the filter on the backendRef instead of the route |
@arkodg |
@MregXN by forwarding operations, do you mean appending headers to the request or response ? |
@arkodg |
@MregXN hi, is there any process? |
I think this is a reasonable request for filter implementation, thoughts on this @arkodg ? |
I haven't started as I think we haven't reached a consensus yet. |
BackendRef Filters are needed by Knative - knative-extensions/net-gateway-api#566 We specifically append headers after a traffic split - this enables our scale to zero feature as well as our ability to handle 'burst capacity' |
I miscalculated the effort to get this in :(
The only issue I see is, there is no support for these specific filters at the weighted cluster level
|
@cnvergence planning on working on this one ? |
sure, I can continue on this one |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
I have encountered difficulties while using the Kubernetes Gateway API Filters under BackendRefs. Is the current envoy gateway already supported?
The text was updated successfully, but these errors were encountered: