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

Add support for InitialCooldownPeriod #1213

Open
Tracked by #1221
shayrybak opened this issue Dec 11, 2024 · 1 comment · May be fixed by #1212
Open
Tracked by #1221

Add support for InitialCooldownPeriod #1213

shayrybak opened this issue Dec 11, 2024 · 1 comment · May be fixed by #1212

Comments

@shayrybak
Copy link

Proposal

Add support for the scaled object generated by the HTTPScaledObject to have it's initialCooldownPeriod defined.

Add the field InitialCooldownPeriod to the httpScaledObject spec.

The generated ScaledObject should have the same value.

Opened a PR to add this functionality.

Use-Case

In our use case we use the HTTP addon to deploy sandbox environments for developers. and we use the http scaler to scaled them to 0 when no requets are happening for some time to reduce costs. however without this option, the users have to first make some requests for the sandbox to be available after the deployment.
with this feature the replicas can be up for some time right after the deployment.

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response

Copy link

stale bot commented Feb 9, 2025

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 Feb 9, 2025
@wozniakjan wozniakjan removed the stale All issues that are marked as stale due to inactivity label Feb 10, 2025
@wozniakjan wozniakjan moved this from To Triage to In Progress in Roadmap - KEDA HTTP Add-On Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants