-
Notifications
You must be signed in to change notification settings - Fork 679
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
Per IP rate limit? #6411
Comments
Hey @sabershahhoseini! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Contour. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace |
Envoy's local rate limit filter does not offer more advanced mechanisms for filtering requests or applying different requests based on source IP this can be achieved using global rate limiting and using the request source IP in a descriptor that the rate limit server applies a specialized rate limit for, see: https://projectcontour.io/docs/1.28/config/rate-limiting/#global-rate-limiting |
The Contour project currently lacks enough contributors to adequately respond to all Issues. This bot triages Issues according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
The Contour project currently lacks enough contributors to adequately respond to all Issues. This bot triages Issues according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
Is there any way to apply per IP rate limit? Seems like local rate limits do not care about IP and only thing is they care is how many requests are given to upstream service.
I mean, if someone just bulk requests to my service, anyone else gets 429? It's not good!
The text was updated successfully, but these errors were encountered: