Deploy Stack to Server Group or Specific Tag #220

New Issue

2025-10-31T15:05:27-05:00

GiteaMirror commented

2025-10-31 15:05:27 -05:00

Originally created by @jo-chemla on GitHub (Feb 18, 2025).

It would be useful to add the ability to deploy a docker-compose stack(s) to multiple server resources at once. This could be done by adding another Resource type, namely Server Groups, or relying on tags to do so. The UI to select where to deploy the stack could remain as-is, with the ability to select in addition to servers, either a tag or server group.

The way Portainer uses Edge Agents Groups is a bit convoluted (Static via selection of all agents, or Dynamic based on filtering via tags), but can be a good start for the inspiration - see the blog posts part 1 / part 2, guide and doc.

A similar feature has been discussed in Procedure Filters here https://github.com/moghtech/komodo/issues/44

Originally created by @jo-chemla on GitHub (Feb 18, 2025). It would be useful to add the ability to deploy a docker-compose stack(s) to multiple server resources at once. This could be done by adding another Resource type, namely `Server Groups`, or relying on tags to do so. The UI to select where to deploy the stack could remain as-is, with the ability to select in addition to servers, either a tag or server group. The way Portainer uses Edge Agents Groups is a bit convoluted (Static via selection of all agents, or Dynamic based on filtering via tags), but can be a good start for the inspiration - see the blog posts [part 1](https://www.portainer.io/blog/using-the-portainer-edge-agent-edge-groups-and-edge-stacks-part-1) / [part 2](https://www.portainer.io/blog/using-the-portainer-edge-agent-edge-groups-and-edge-stacks-part-1-0), [guide](https://downloads.portainer.io/edge_agent_guide.pdf) and [doc](https://docs.portainer.io/advanced/edge-agent). A similar feature has been discussed in Procedure Filters here https://github.com/moghtech/komodo/issues/44

GiteaMirror added the seen 👀 label 2025-10-31 15:05:27 -05:00

GiteaMirror commented

2025-10-31 15:05:28 -05:00

@Eldiabolo21 commented on GitHub (Mar 8, 2025):

I was just looking for the same!

I wouldn't want Komodo to become another container orchestrator, but simple functionality run a container with the same parameters on mulitple hosts would be great!

@Eldiabolo21 commented on GitHub (Mar 8, 2025): I was just looking for the same! I wouldn't want Komodo to become another container orchestrator, but simple functionality run a container with the same parameters on mulitple hosts would be great!

GiteaMirror commented

2025-10-31 15:05:28 -05:00

@Badn1nja commented on GitHub (Mar 10, 2025):

This would be a really cool feature. I think it could be implemented by repeating a deployment for the servers selected in the deployment where at the moment it's 'deployment per server'

@Badn1nja commented on GitHub (Mar 10, 2025): This would be a really cool feature. I think it could be implemented by repeating a deployment for the servers selected in the deployment where at the moment it's 'deployment per server'

GiteaMirror commented

2025-10-31 15:05:28 -05:00

@huzky-v commented on GitHub (Mar 18, 2025):

Just my experience. If you want to kind of "batch-deploy" the stack by tag name, you can do it by "Actions" with something like that:

const autoDeploy = await komodo.read('ListStacks', {query: {tags: ["auto-deploy"]}});
await Promise.all(autoDeploy.map((item) => komodo.execute('DeployStack', {stack: item.id})));

where the stack tagged in Komodo is auto-deploy
Little bit of code involved, but works for me

@huzky-v commented on GitHub (Mar 18, 2025): Just my experience. If you want to kind of "batch-deploy" the stack by tag name, you can do it by "Actions" with something like that: ``` const autoDeploy = await komodo.read('ListStacks', {query: {tags: ["auto-deploy"]}}); await Promise.all(autoDeploy.map((item) => komodo.execute('DeployStack', {stack: item.id}))); ``` where the stack tagged in Komodo is `auto-deploy` Little bit of code involved, but works for me

GiteaMirror commented

2025-10-31 15:05:29 -05:00

@nano9g commented on GitHub (Jun 14, 2025):

In case it’s helpful to anyone, I ran into this recently and wrote an action that will clone stacks between servers based on tags.

@nano9g commented on GitHub (Jun 14, 2025): In case it’s helpful to anyone, I ran into this recently and wrote an [action](https://gist.github.com/nano9g/95190ab06bf34c9a12691b3b493e92eb) that will clone stacks between servers based on tags.

GiteaMirror commented

2025-10-31 15:05:29 -05:00

@danielwerner86 commented on GitHub (Jun 30, 2025):

I'd just like to agree that this would be an awesome feature.
Instead of a dropdown with the server you want to deploy on, you could select multiple servers and deploy on all.

@danielwerner86 commented on GitHub (Jun 30, 2025): I'd just like to agree that this would be an awesome feature. Instead of a dropdown with the server you want to deploy on, you could select multiple servers and deploy on all.