Closed Spoonbender closed 2 years ago
related to https://github.com/solo-io/gloo/issues/5650
@nfuden can you share what user config are you planning to expose to make this configurable?
@nrjpoddar its a good question and one that is not entirely set.
The current statements are under consideration.
Current thought is to have an option in GlooOptions which would have information for allow-listing/deny-listing and an array of plugins to allow/disallow. Similar to the basic flow for DisableGrpcWeb. Would be distinct from a disable flag.
So far I've been digging in on a per filter to see what it means for a filter to not be needed in a given configuration and need to get some feedback on the settings naming/structuring.
Is there a specific version requested for backports? Or are we fine with it being in 1.11?
Bulldozer closed when it merged to OSS, still needs to be brought into Enterprise so reopening.
Is your feature request related to a problem? Please describe. Currently, the filter chains constructed by Gloo Edge include various filters which we don't actually use, such as: -
io.solo.filters.http.solo_jwt_authn_staged
-envoy.filters.http.ext_authz
-envoy.filters.http.grpc_web
-envoy.filters.http.ratelimit
-io.solo.filters.http.graphql
This is poses two issues:
Notice that in a "vanilla" envoy - no filters are added to the chain unless explicitly configured to.
Describe the solution you'd like Gloo should only add filters to the chain if they are actually in use. For example:
Describe alternatives you've considered