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

cron scaler metricType shouldn't be configurable #3591

Closed
amirschw opened this issue Aug 24, 2022 · 6 comments
Closed

cron scaler metricType shouldn't be configurable #3591

amirschw opened this issue Aug 24, 2022 · 6 comments
Assignees
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity

Comments

@amirschw
Copy link
Contributor

Proposal

For the cron trigger to scale to the number specified in metadata.desiredReplicas, it must use the AverageValue metric type. Otherwise (if Value is used), based on the HPA algorithm, it will scale to [currentReplicas * desiredReplicas] instead. Therefore, we should probably disallow changing the metricType for this specific scaler.

Use-Case

No response

Anything else?

Related to #2309 where we introduced the option to set the metricType.

@amirschw amirschw added feature-request All issues for new features that have not been committed to needs-discussion labels Aug 24, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Aug 24, 2022
@amirschw
Copy link
Contributor Author

Will be happy to do it myself if there's no objection

@JorTurFer
Copy link
Member

JorTurFer commented Aug 24, 2022

Makes sense, excellent catch!

I have already assigned this issue to you ❤️

@tomkerkhove
Copy link
Member

Not sure if we should continue investing in cron-scaler or should start #3566 with this instead

@amirschw
Copy link
Contributor Author

Thanks, I'll wait for the outcome of the discussion there before starting this.

@stale
Copy link

stale bot commented Oct 23, 2022

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 Oct 23, 2022
@stale
Copy link

stale bot commented Oct 31, 2022

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Oct 31, 2022
Repository owner moved this from Proposed to Ready To Ship in Roadmap - KEDA Core Oct 31, 2022
@JorTurFer JorTurFer moved this from Ready To Ship to Done in Roadmap - KEDA Core Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity
Projects
Archived in project
Development

No branches or pull requests

3 participants