You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rate limit policies are configured in the Control Plane or defined using Ratelimit CRD with API, HTTP Route, Application and Subscription CRDs. Once Ratelimits are in an internal Data Structure (Ratelimits got from CP or CRDs) to the Agent, the Agent should configure Enforcer, Router, and Ratelimit service with Ratelimit policies.
For inline rate limits (Ratelimits are defined by the API creator by just typing the number of requests in an input box and selecting the unit time from a selection with conditional rate limits) it is able to use the same name for the same limits (to reuse the same policy, otherwise the rate limit config will be larger).
For example 10 req/min: "$_10_per_min"
But there could be cases something like the following.
The same 10 per min policy with different conditional policies.
Eg:
Policy1: 10 per min, c1 - IP Range(1,2)
Policy2: 10 per min, c1 - IP Range (2,3)).
Append UUIDs of conditions to the name ("$_10_per_min_UUID1", "$_10_per_min_UUID2", "$_10_per_min_default"). This has to be decided.
renuka-fernando
changed the title
Configure Rate limit policies in Choreo Connect components
[Rate limiting] Configure Rate limit policies in Choreo Connect components
Oct 31, 2022
Description
Rate limit policies are configured in the Control Plane or defined using Ratelimit CRD with API, HTTP Route, Application and Subscription CRDs. Once Ratelimits are in an internal Data Structure (Ratelimits got from CP or CRDs) to the Agent, the Agent should configure Enforcer, Router, and Ratelimit service with Ratelimit policies.
The text was updated successfully, but these errors were encountered: