net-contour: rate limiting in contour HTTP Proxy spec

[pramenn]

Describe the feature

I am currently using net contour controller config which does not support enabling rate limiting in contour HTTP Proxy spec for my knative services.

Http Proxy with global rate limiting example: https://projectcontour.io/docs/v1.21.0/config/rate-limiting/#global-rate-limiting
Contour rate limiting design doc: https://github.com/projectcontour/contour/blob/main/design/ratelimit-design.md

configmap config-contour in knative-serving namespace should support contour HTTP Proxy rate liming spec.

[pramenn]

/area networking

[nak3]

This is related to knative-extensions/net-kourier#759 (rate limiting for net-kourier).

What I am still debating is whether we should add it as a common API or not.
I keep watching Gateway API's discussion kubernetes-sigs/gateway-api#326 (as we will use the API in the future), but they also do not have the conclusion yet.

[pramenn]

@nak3 Thanks.

PR is for net-kourier but I am using net-contour. Besides, PR only supports local rate limiting, is implementing global rate limiting descriptor on the roadmap?

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[knative-prow-robot]

This issue or pull request is stale because it has been open for 90 days with no activity.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close

/lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[knative-prow-robot]

This issue or pull request is stale because it has been open for 90 days with no activity.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close

/lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.