argoproj / argoproj/argo-workflows
blackout time support
Open
area/cron-workflows
solution/workaround
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
allow configuring ALL CronWorkflows (or even normal workflows) with a time range that they CANNOT start inside
# Use Cases
My target DB that my workflows write data to has a weekly outage at a pre-defined 30 minute block
Contributor guide
Research direction
Start by tracing the CronWorkflow and normal workflow scheduling entry points to understand where start eligibility is decided. The issue does not name files or tests; done would require an agreed configuration model for blackout ranges and verification that workflows cannot start during the configured outage window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100