Proposal: Horizontal service Autoscaling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
I have been working with docker SWARM lately and noticed there is a lack of features Horizontal service Autoscaling.
Currently we have shell script that scale UP/DOWN containers as new servers get added/removed to cluster but it would be amazing feature if swarm manager can automatically scale up/down containers to match average CPU utilization specified by user.
Swarm manager should periodically adjusts the number of replica in a service to match average CPU utilization to the target specified by user.
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 tracing how the swarm manager tracks services, replicas, and node CPU utilization; review existing scheduling and service-update behavior. Done should be defined by an agreed autoscaling design, including target utilization, adjustment timing, replica limits, and tests for scale-up and scale-down behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100