Skip to content
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

Expose the default rate limiter #443

Merged
merged 1 commit into from
Jan 10, 2023
Merged

Expose the default rate limiter #443

merged 1 commit into from
Jan 10, 2023

Conversation

darkowlzz
Copy link
Contributor

The default configurations for rate limiter is exposed only to flag set. This change adds a new function GetDefaultRateLimiter() to provide access to the same rate limiter configuration without flags. This is useful for setting the default rate limiter for reconcilers in test suites.
The default rate limiter configuration set in upstream client-go code has a very short minimum delay, which results in a flood of error logs in the tests when it's an expected behavior. Because the reconcilers are configured differently in the test suite and a properly deployed controller, there is a difference in the observed results. This change allows for the test and deployment configuration of the reconcilers to be similarly configured with the same default rate limiter.

@darkowlzz darkowlzz added the area/runtime Controller runtime related issues and pull requests label Jan 4, 2023
Copy link
Member

@souleb souleb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

The default configurations for rate limiter is exposed only to flag set.
This change adds a new function GetDefaultRateLimiter() to provide
access to the same rate limiter configuration without flags. This is
useful for setting the default rate limiter for reconcilers in test
suites.

Signed-off-by: Sunny <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/runtime Controller runtime related issues and pull requests
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants