argoproj / argoproj/argo-workflows

Allow staggering of cron workflows with identical schedules

Open
#5,956 2 comments 3 reactions 0 assignees View on GitHub
area/cron-workflows solution/workaround
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

Allow cron workflow schedules to be set up in such a way that multiple workflows with identical schedules don't all start at the exact same time. This will prevent sudden surge in loads. Jenkins supports this feature, see [here](https://stackoverflow.com/questions/47302607/meaning-of-h-5-in-cron-jenkins) for a description.

# Use Cases

The controller could use this mechanism to stagger the launching of each workflow by a few seconds/minutes if there are cron workflows configured with identical schedules, for example, run once per day at 9 am.

---

**Message from the maintainers**:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified in the issue. Start by tracing how the controller schedules cron workflows, then determine how identical schedules should be detected and staggered; done means configured workflows no longer launch simultaneously and existing scheduling behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.