-
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
scaledObject name is not specified #6337
Comments
Are there any other HPA instances running in Kubernetes? |
Yes there are old HPAs not created by scaled objects |
These logs are normal since all HPAs will query the metric value in KEDA's metric adapter, and old HPAs will be blocked. |
Ah, the error message still confusing because there was no scaledobject in the cluster, and the logs polluted our logging platform. for anyone facing this, I had to scale down |
Report
I installed keda in EKS 1.29 using helm chart via terraform, using the following snippet:
I tried keda
2.14
,1.15
,2.16
I didn't create any scaled object yet
Expected Behavior
Keda working find and no error logs.
Actual Behavior
I'm getting lot of logs from
keda-operator-metrics-apiserver
as follows:Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.16.0
Kubernetes Version
1.29
Platform
Amazon Web Services
Scaler Details
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: