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.

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

How to combine this with other Keda triggers #816

Closed
kjfly opened this issue Oct 9, 2023 Discussed in #455 · 3 comments
Closed

How to combine this with other Keda triggers #816

kjfly opened this issue Oct 9, 2023 Discussed in #455 · 3 comments
Labels
stale All issues that are marked as stale due to inactivity

Comments

@kjfly
Copy link

kjfly commented Oct 9, 2023

Discussed in #455

Originally posted by tidunguyen May 20, 2022
I want to use multiple triggers for my deployment. How can I combine this tool with other Keda triggers so that my app can be activated whenever any trigger run.
I tried to edit the auto-created ScaledObject created by this controller and managed to trigger the app. However, it does not work as expected in several cases. For example:

  • CooldownPeriod is always 300s no matter how much I set
  • App does not get scaled down occasionally
  • Sometimes, app is stucked in a scaled up then terminated instantly loop

What is the idiomatic way to do this or this use case is not yet supported and is supposed to give undefined behaviors?

@JorTurFer
Copy link
Member

Hi!
Currently it's not possible but this on-going PR allows to not generating the ScaledObject from HTTPScaledObject, so you will have the option to treat the HTTP metrics source as an external source on your own ScaledObject (and this unlocks all the options already supported but the ScaledObjects)

@JorTurFer JorTurFer moved this from To Triage to In Progress in Roadmap - KEDA HTTP Add-On Oct 16, 2023
Copy link

stale bot commented Dec 15, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Dec 15, 2023
Copy link

stale bot commented Dec 22, 2023

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Dec 22, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Roadmap - KEDA HTTP Add-On Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale All issues that are marked as stale due to inactivity
Projects
Status: Done
Development

No branches or pull requests

2 participants