operator can auto-scale worker pods based on the tasks queue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Operator should be able to monitor tasks queue and if there are a lot of tasks in waiting state it should scale up temporarily worker pods because it means there are not enough of workers to process tasks( bottleneck).
Then operator should scale down worker pods once the task queue is empty (no bottleneck). Scaling down is important so pods do not consume resources in vain.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context about the feature request here.
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
The issue names no files, tests, or entry points, so start by locating the operator's worker-pod reconciliation and task-queue integration. Done means worker pods scale up when waiting tasks indicate a bottleneck and scale down after the queue is empty, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100