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

Investigate "client-side throttling, not priority and fairness, request" when running the audit scanner #280

Open
fabriziosestito opened this issue May 24, 2024 · 0 comments

Comments

@fabriziosestito
Copy link
Contributor

Is your feature request related to a problem?

The audit scanner was reported to cause client-side throttling when creating or updating policy report

Waited for 1.000137379s due to client-side throttling, not priority and fairness, request: GET:(omitted)/policyreports/4771d2aa-2573-4b47-961f-0d4fe9d8a9b1)

Solution you'd like

Maybe we need to tune QPS/Burst of the k8s client:

https://pkg.go.dev/k8s.io/client-go/rest#Config

	// QPS indicates the maximum QPS to the master from this client.
	// If it's zero, the created RESTClient will use DefaultQPS: 5
	QPS float32

	// Maximum burst for throttle.
	// If it's zero, the created RESTClient will use DefaultBurst: 10.
	Burst int
	
	// Rate limiter for limiting connections to the master from this client. If present overwrites QPS/Burst
	RateLimiter flowcontrol.RateLimiter

Alternatives you've considered

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant