-
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
cron scaler metricType shouldn't be configurable #3591
Comments
Will be happy to do it myself if there's no objection |
Makes sense, excellent catch! I have already assigned this issue to you ❤️ |
Not sure if we should continue investing in cron-scaler or should start #3566 with this instead |
Thanks, I'll wait for the outcome of the discussion there before starting this. |
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. |
This issue has been automatically closed due to inactivity. |
Proposal
For the cron trigger to scale to the number specified in
metadata.desiredReplicas
, it must use theAverageValue
metric type. Otherwise (ifValue
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.
The text was updated successfully, but these errors were encountered: