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
The rate limits for the application are set at 6 requests/second per client.
When KEDA scales the application from 3 replicas to 6, it would be beneficial if the rate-limiting configuration in Envoy Gateway automatically adjusted to reflect this change. For instance, the rate limit should scale to 12 requests/second (calculated as the default rate limit per replica multiplied by the number of replicas).
Proposal:
Introduce a controller that helps dynamically adjusts API Gateway settings - such as rate limits or request thresholds - based on changes in the deployment.
Why Envoy Gateway?
I chose Envoy Gateway as the example because it’s a progressive implementation of Gateway APIs. However, this controller concept could be designed to work across different vendors to ensure flexibility and scalability.
Use-Case
This feature would significantly enhance the adaptability of API Gateways to dynamic environments, improving both performance and user experience.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Proposal
Referenced from: GitHub Issue #4447
Scenario:
Proposal:
Introduce a controller that helps dynamically adjusts API Gateway settings - such as rate limits or request thresholds - based on changes in the deployment.
Why Envoy Gateway?
I chose Envoy Gateway as the example because it’s a progressive implementation of Gateway APIs. However, this controller concept could be designed to work across different vendors to ensure flexibility and scalability.
Use-Case
This feature would significantly enhance the adaptability of API Gateways to dynamic environments, improving both performance and user experience.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered: