-
Notifications
You must be signed in to change notification settings - Fork 998
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 Unable to Retrieve correct Kafka Metrics from ScaledObject on GKE #5730
Comments
Could you change the log-level to debug in operator and send the operator logs? |
In addition to the log, could you provide the |
sorry for the delay, I still have this issue and created a new GCP/GKE cluster specially to debug it. I was able to reproduce the issue and got the logs from the exact moment where the current metric value switch in the HPA from the logs from the controller when this switch happened:
the scaled object:
|
found people with similar issue https://kubernetes.slack.com/archives/CKZJ36A5D/p1709761505122509 |
@SpiritZhou @dttung2905 yesterday I created an EKS cluster with the same GCP setup/versions, and it works perfectly. Can you think of anything that could be different for GCP and AWS? any kind of blocker or anything that could be causing the issue? I have also followed the k8s events and couldn't find anything bad in GCP. |
Report
KEDA is unable to retrieve metrics correctly from a ScaledObject/ScaleTarget using a Kafka trigger when deployed to a GKE cluster (It works locally)
Expected Behavior
When HPA calculates the current metric value, it should not return
-9223372036854775808m
, but a valid Kafka lag.Actual Behavior
When the Kafka ScaledObject is deployed to GKE:
Steps to Reproduce the Problem
Logs from KEDA operator
There is no error or warning in the Keda operator.
KEDA Version
2.13.1
Kubernetes Version
1.27
Platform
Google Cloud
Scaler Details
Kafka
Anything else?
No response
The text was updated successfully, but these errors were encountered: