Allow pin/sticky containers when using swarm
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
For stateful containers (e.g. a posgres database) it would be very helpful to specifically select which host machine this container should be pinned to. Since the volumes are local in swarm, one has to prevent the container switching to different hosts machines.
Describe the solution you'd like
This currently requires editing the cluster options in the advanced options which works but a better user experience would be a (multi)select in the ui which allows to specify the nodes in the swarm the container is restricted to. This would provide a better user experience.
Will you send a PR to implement it?
Maybe, need help
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 or tests; start by tracing the existing advanced cluster options and the Swarm deployment UI. Done means the UI can select one or more Swarm nodes for a stateful container and applies that restriction during deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100