actions / actions/actions-runner-controller
Feature Request: Schedule-based minRunners Configuration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
I suggest enhancing the user experience by providing the ability to dynamically control minRunners based on the time of day and the day of the week, similar to cron syntax. This would allow users to adjust the minRunners parameter to suit their particular needs. For instance, from 9:00 to 18:00 on weekdays, one might want to set minRunners to 10. After business hours, where the workload is likely reduced, we could then set it to 0.
Why is this needed?
Currently, it seems that the minRunners setting is static and needs manual intervention to change. With dynamic settings, the system will be able to better adapt to differing workload patterns and would improve overall performance and efficiency.
Additional context
The proposed enhancement would be useful for organizations that have clear busy periods. This change could directly impact cost savings by allowing a reduction in resources during quiet periods, whilst still providing ample resources during busy periods. Furthermore, it could promote more effective use of resources and avoid resource waste.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating how minRunners is configured and reconciled, then clarify the schedule syntax, timezone behavior, and precedence rules; done means a documented, tested way to vary minRunners by time and weekday.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100