Replies: 1 comment 1 reply
-
|
Also miss this spec, same use case of goat-ssh here. Filters make a lot of sense for HTTPRoute and so does it for TLSRoutes. As Gateway API's BackendRef Filters seems to model middlewares (as some general spec-agnostic/vendor-specific request processors), so this makes a lot of sense and fills a lot of use cases for TLSRoutes also. |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
rules.backendRefs.filters.extensionRefsfunctionality is available for HTTPRoute, but not for TLSRoutes.My primary use case is to enable Traefik's Middleware IPAllowlist, so that i don't need to modify Gateway's
loadBalancerSourceRangesfor every route which is added. This should unlock many more cases.Beta Was this translation helpful? Give feedback.
All reactions