Support local ratelimit

[zhaohuabing]

Description:
Support local ratelimt as described in envoy Local rate limit doc.

Global ratelimit and local ratelimit are used in different scenarios:

• If you want to enforce a global access control policy to a particular resource, then global rate limiting should be used. A typical scenario is to set how often a user can access an API according to the user’s service level agreement. Docker Hub, for example, has a rate limiting policy for how often a user can pull images from its registy. Paid users have a higher quota than free users.

• Local ratelimit is very useful when proxy instances can be horizontally scaled out based on the client load. In this scenario, since each proxy instance get its own rate limit quota, the traffic that the fleet of envoy proxies can handle increase when more proxy instances are spun up.

[arkodg]

+1 for this, the API could mimic/reuse existing data structures that exist from GlobalRateLimit

gateway/api/v1alpha1/ratelimitfilter_types.go

Line 53 in 9d6d699

type GlobalRateLimit struct {

The only issue I see is supporting the Distinct match case, which needs some upstream work
envoyproxy/envoy#23351
cc @cpakulski @vikaschoudhary16

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.