New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scale ratelimit with ingress pods #5113
base: main
Are you sure you want to change the base?
Conversation
👷 Deploy request for nginx-kubernetes-ingress pending review.Visit the deploys page to approve it
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM docs-wise, but most of the PR is code-based, so I am not approving.
@shaun-nx What do you think? Does this look fine or are any changes required? |
Just an FYI as this has been lingering for review. |
d417459
to
33c3828
Compare
docs/content/configuration/ingress-resources/advanced-configuration-with-annotations.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Jim Ryan <j.ryan@f5.com> Signed-off-by: dbaumgarten <mail@dbaumgarten.net>
8489a7e
to
fbd67bd
Compare
Proposed changes
Implements #4894
Add a flag (in VS-Policy and in Ingress-Annotations) to enable ratelimit-scaling. If enabled, the configured ratelimit is divided by the number of currently active ingress-pods. This way the total sum of the ratelimit stays constant, even when autoscaling changes the number of nginx-ingress pods.
Checklist
Before creating a PR, run through this checklist and mark each as complete.