Replies: 2 comments
-
Anyone?? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ok, the issue seems to be that we have kube-adapter-metrics already on the cluster and you can't have more than 1 external metrics server |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have created it under Q&A, but as I didn't get any response I'm creating it here as well for more visibility
I'm trying to setup Keda for the first time with a sample application scaling based on AWS SQS queue
Based on my understanding of how Keda works:
I have set the keda namespace
It contains 2 pods running on it: keda-operator and keda-metrics-apiserver
There is a
ScaledObject
defined to handle the scaling of a sample application scaling based on an SQS QueueThe scaled object is as follows:
I have created an IAM role and I'm using its role to attach it to the operator pod and metrics-server pods
The Keda-managed scaling process works fine, the pods manage to scale from 0 to 1 and from 1 to 0
However, that is all we get
When it delegates the scaling to the HPA it fails to collect the metrics with the following warning(that looks like an error) coming from the
kube-metrics-adapter
Apparently it miss a plugin to collect the metric (?)
I can't find anything on Keda documentation regarding plugin installation or some extra setup needed
I also tried querying the external metrics API and I don't see the metrics there:
The
keda-operator
logs don't show any error and scale nicely from 1 to 0 and vice-versaI found this Github issue but the solution was to add the permission to the worker node role, which I don't think is the right for this situation
Any idea where else I could look into?
Beta Was this translation helpful? Give feedback.
All reactions