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

Suggest using CronJobs in Cron scaler docs for recurring scaling #703

Open
tomkerkhove opened this issue Mar 9, 2022 · 5 comments
Open
Assignees
Labels
cant-touch-this All issues that should not be automatically closed by our stale bot documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@tomkerkhove
Copy link
Member

tomkerkhove commented Mar 9, 2022

Suggest using CronJobs in Cron scaler docs for recurring scaling which we don't support, but sometimes confuses people.

This is a scheduling need, not a scaling need.

@tomkerkhove tomkerkhove added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Mar 9, 2022
@stale
Copy link

stale bot commented May 8, 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.

@tomkerkhove tomkerkhove self-assigned this May 8, 2022
@tomkerkhove tomkerkhove added the cant-touch-this All issues that should not be automatically closed by our stale bot label May 8, 2022
@kai-66degrees
Copy link

@tomkerkhove I am working on a similar use case and I was exploring if KEDA fit the needs. What is the meaning of "recurring scaling which we don't support"?
Can I not create a ScaledObject with a cron trigger for a deployment (like in the docs example) and scale it to the desired replicas/min replicas, and define another ScaledObject with a different timeslot and minReplicaCount to scale it again?

@tomkerkhove
Copy link
Member Author

This is how our current CRON scheduler works:

image

See https://keda.sh/docs/latest/scalers/cron/#how-does-it-work.

This issue, however, is to document the scenario where you want to scale every x minutes/hours/etc.

@teebu
Copy link

teebu commented May 30, 2022

I dont understand what this means. This statement is confusing.

What the CRON scaler does not do, is scale your workloads based on a recurring schedule.

Isn't a cron a recurring schedule? Meaning during the day I want my min pods ot scale to 10?

Can you clarify with a scenario on the statement what it doesn't mean. I think you're trying to say the end time is required for this to function.

@tomkerkhove
Copy link
Member Author

Cron is used as a time notation when to start/end. By doing this, you define a window to which we will scale the workload correspondingly.

It does not mean, "scale every x min/h/days". For that, Kubernetes has CronJobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cant-touch-this All issues that should not be automatically closed by our stale bot documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants