-
Notifications
You must be signed in to change notification settings - Fork 685
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
Allow use of any envoy HTTP filter #4606
Comments
Hi @carlin-q-scott , filters are generally a feature of Edge Stack but we do have users who build their own features to work with Emissary. Could you tell us more about your use case for this Envoy http filter and point to the relevant link there? |
We are investigating a similar use case is to load proxy wasm filter into envoy like below:
Is there any plans to implement EnvoyFilter CRD or what alternative you can suggest? |
Not exposing Envoy filters directly reduces the effective power from using Envoy in the first place. In our case, we would like to be able to use Lua scripting to do some custom mitigations for certain types of attacks. |
@chendo did you find a way by any chance? |
Also looking a way to use a custom envoy filter in emissary installation |
Are there any plans to include Filter & FilterPolicy CRD's from AES into Emissary? We are trying to add signal sciences agent as a sidecar to our emissary but it can't reroute traffic to the sidecar without these 2 CRD's. |
Please describe your use case / problem.
I would like to use a built-in envoy http filter, but I see no way of enabling or configuring it with emissary-ingress.
Describe the solution you'd like
Create a ConnectionManager CRD with an http_filters property for configuring any http_filter that's available through envoy. Or create something like the Filter CRD from EdgeStack in the base emissary-ingress and allow us to configure envoy filters through that.
Describe alternatives you've considered
Export the generated envoy.json from a running stack, add the filters to that, then mount the file to the container in the base config folder.
Additional context
The text was updated successfully, but these errors were encountered: