Keda + GKE "Unable to read all metrics" issue #1853
-
ReportWe are using Keda 2.2.0 in GKE with k8s 1.18 to scale a Deployment based with the redis trigger. Both the scaled object and deployment are defined in the same namespace. The minimum amount of replicas is set to 0, max to 5. When adding items to the redis list, KEDA scales from 0 -> 1. The HPA does not scale any further as the autoscaler status is "Unable to read all metrics". When the list is empty again, KEDA also scales back from 1 -> 0. How can I best figure out why the HPA is not able to read all metrics? Expected BehaviorThat the metrics are read and used to orchestrate the scaling. Actual BehaviorWhen adding items to the redis list, KEDA scales from 0 -> 1. The HPA does not scale any further as the autoscaler status is "Unable to read all metrics". Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version2.2.0 Kubernetes Version1.18 PlatformGoogle Cloud Scaler DetailsNo response Anything else?No response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Can you share the output of your kubectl commands please? |
Beta Was this translation helpful? Give feedback.
-
When diving into the documentation we found out that we needed to add the firewall rule, many thanks for replying, awesome technology :-) |
Beta Was this translation helpful? Give feedback.
When diving into the documentation we found out that we needed to add the firewall rule, many thanks for replying, awesome technology :-)