-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
KEDA : Client rate limit issues #6359
Comments
Hello |
Hi @JorTurFer
|
Hello, Reducing the information sent to the k8s API related with fallback when fallback is enabled is more complex and will be done with the refactor of the logic, but this PR (shipped as part of v2.16.0) reduces significantly the amount of traffic related with fallback when the fallback feature isn't enabled for the given SO |
Report
Running into multiple
client rate limiter Wait returned an error
issues in keda-operator. We have around 50-100 scaled objects across various EKS clusters and this problem seen after we upgraded KEDA from 2.13.0 to 2.15.1 version.We have a varying number of ScaledObjects across our eks clusters, and as per previous threads we previously increased the qps values but since upgrade we are getting frequent errors.
Our K8s client config is as follows:
I want to understand that what is the reason KEDA sends so many concurrent requests to the kubernetes api server? Since we do not have a very large number of scaledobjects and default
polling_interval
of 30sec is used, why the keda client is ratelimiting the requests? Need to understand if the keda retries are causing issues or is it something else?Expected Behavior
We should not run into client rate limit issues.
Actual Behavior
We are getting error messages in keda-operator logs for client rate limit issues.
Steps to Reproduce the Problem
Observed in cluster with scaledobjects around 50-100 with keda version 2.15.1 and eks version 1.31.
Logs from KEDA operator
KEDA Version
2.15.1
Kubernetes Version
1.31
Platform
Amazon Web Services
Scaler Details
CpuMemoryScaler & PrometheusScaler
Anything else?
No response
The text was updated successfully, but these errors were encountered: