Ability to configure forced stateless mode for swarm based deployment
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?
The way docker swarm works is it's fully robust for stateless services but not as much for stateful services. For stateful services (those that have mounted volumes), we need to take care of sharing data (can be done via docker plugins).
Describe the solution you'd like
It would be great if we could add in a setting that allows for state to be stored in the server or not. That way stateful services are not accidentally deployed when on swarm mode.
It can also come in as a user permission field, to allow state mount
Describe alternatives you've considered
Not using the volume feature would work, but I do think it'd be great if the admin can configure it to be unavailable for other user.
Additional context
No response
Will you send a PR to implement it?
No
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
Start by locating the swarm-based deployment flow and the code that handles mounted volumes and user permissions. Clarify whether the setting belongs to server configuration or per-user permissions, and define how disabled state mounts should be reported and enforced. Done means the chosen configuration prevents unintended stateful deployments without affecting stateless services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100