-
Notifications
You must be signed in to change notification settings - Fork 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
apiserver received an error "exactly one scaled object should match label " #1344
Comments
Do you have anything else installed on the cluster that could eventually use External Metrics? (Datadog, k8s-prometheus-adapter etc?) |
Yes, I have the prometheus-adapter installed. |
Both projects are using the same external metrics provider, they cannot be installed on the cluster at the same time. With your KEDA installation, you have just replaced the Metrics Server from prometheus-adapter, which is not working currently. The errors you see are requests from prometheus-adapter, which is polling a wrong Metrics server. Unfortunately this is a limitiation of kubernetes, see this: kubernetes-sigs/custom-metrics-apiserver#70 |
got it. Thank you. |
Hey @wiseelf, did it get resolved for you after removing prometheus-adapter? We are encountering the same errors even after removing prometheus-adapter. We dont have cloudwatch-adapter either. |
@CarloColumna yes, removing prometheus-adapter helped. |
Thanks for that @wiseelf ! |
If someone else ends up in here, I managed to sort out the issue by deleting all the old HPAs that were created by |
Hello!
Actual Behavior
Right after the installation keda-metrics-apiserver shows a lot of errors in the logs.
I haven't configured any ScaledObjects yet.
Why does this happen? Is it critical?
Expected Behavior
No errors in the log
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: