configuring rate limit filter
Type of change
- Bug Fix
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
Does this introduce a change in the cloud provider implementation, if so which cloud?
Does this introduce a breaking change?
What is the current behavior?
Currently, no rate limiting is applied on service which can limit the count of users accessing it.
What is the new/expected behavior?
The service will have specific token count which will set limit to restrict number of users using the service per cycle.
Have you added/updated Unit Tests and Integration Tests?
Any other useful information
Added Envoy filter to apply rate limiting. Added support to generate yaml file via Helm in deployment itself. Initially value of applying rate limit filter is set to false. It can be set while installing helm command using following instruction : --set envoyFilter.enabled=true