-
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
KEDA Kafka Scaler : Not able to set activationLagThreshold to '0' value (which is default value supported by KEDA) #4137
Comments
This makes sense totally, are you willing to fix it? |
@JorTurFer Yes, I would be glad to contribute. I'll raise a PR shortly. Can I get write access? |
Nice! I assign this issue to you :) |
Thanks @JorTurFer Raised the PR: #4143 |
Thanks @JorTurFer Will it be released as part of March 2nd, 2023 release? or can be released as part of some patch release? I'm new to KEDA release process and hence the question. :) |
I don't think that we do any other hotfix release before March (we have released v2.9.2 this week, and I'm releasing v2.8.2 right now), but for sure in the next minor release (v2.10 in March) will be included |
Hi @JorTurFer, Can you please share the exact date when we'll be releasing v2.10? Thanks, |
We aim to do on 9th |
Report
KEDA is supporting 0 as the default value for activationLagThreshold in kafka scaler. But if we set this field explicitly with the 0 value, KEDA is throwing below error:
"error":"error parsing kafka metadata: "activationLagThreshold" must be positive number"
A default should always behave the same whether you set it explicitly or leave it, if optional.
Expected Behavior
A default should always behave the same whether you set it explicitly or leave it, if optional.
So even if we set activationLagThreshold as 0, KEDA should not throw any error.
Actual Behavior
KEDA is throwing below error
"error":"error parsing kafka metadata: "activationLagThreshold" must be positive number"
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.9.2
Kubernetes Version
1.26
Platform
Microsoft Azure
Scaler Details
Kafka Scaler
Anything else?
No response
The text was updated successfully, but these errors were encountered: