Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Kafka Scaler: check lagThreshold is a positive number #3367

Merged
merged 1 commit into from
Jul 14, 2022
Merged

Kafka Scaler: check lagThreshold is a positive number #3367

merged 1 commit into from
Jul 14, 2022

Conversation

zroubalik
Copy link
Member

Signed-off-by: Zbynek Roubalik zroubalik@gmail.com

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Tests have been added
  • Changelog has been updated and is aligned with our changelog requirements

Fixes #3366

@zroubalik
Kafka Scaler: check lagThreshold is a positive number
2af9d7d 
Signed-off-by: Zbynek Roubalik <zroubalik@gmail.com>
@zroubalik zroubalik requested a review from a team as a code owner July 14, 2022 12:40
@zroubalik
Copy link
Member Author

zroubalik commented Jul 14, 2022 •
edited by github-actions bot
Loading

/run-e2e kafka*
Update: You can check the progress here

@JorTurFer JorTurFer merged commit 2b8f2fd into kedacore:main Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JorTurFer JorTurFer JorTurFer approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Setting lagThreshold to 0 causes the keda-operator to panic
2 participants
@zroubalik @JorTurFer