Open xuanlinhha opened 2 years ago
Thanks for submitting. We will look into this.
Is there any update?
Hi, I am also facing same issue, is there a solution for this.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Version
1.11.x (latest stable)
Kubernetes Version
No response
Describe the bug
I follow the setup here
https://docs.solo.io/gloo-edge/latest/guides/security/rate_limiting/envoy/
to editdefault
settings & virtualservice (kubectl edit settings default -n gloo-system
&kubectl edit virtualservice default -n gloo-system
) but it doesn't workI am using the Gloo Edge Opensource version, anyone has the same issue with me? Thanks
Steps to reproduce the bug
kubectl edit settings default -n gloo-system kubectl edit virtualservice default -n gloo-system
Expected Behavior
curl <path-to-service>
for multiple times will getToo many requests
in responseAdditional Context
No response