0.6.0 adds Docker Swarm environments, fills in the parts of Compose that stacks left out, and lets a git stack fetch over SSH. Update the image tag and restart; the database migrates on start.
Docker Swarm
In Admin → Environments → Add environment, choose Docker Swarm. You get a key to store as a Docker secret and a stack file that runs fleetops-agent as a global service, one task per node. Deploy it from a manager; nodes that join later get an agent too. FleetOps can run outside the swarm or inside it as a stack of its own.
Every agent shares the key, so the key alone does not say which node it runs on. Each agent signs a challenge with its node’s Swarm key, its certificate is checked against the swarm’s root CA, and a known manager confirms the node is still a member with that role. Before any agent is trusted, an admin compares the swarm’s root CA fingerprint with docker swarm ca and clicks Trust this swarm.
A swarm has an overview that leads with what needs attention, and live pages for nodes, services, tasks, stacks, secrets, configs and networks, with a visualizer and service logs across every task. Drain, promote and label nodes; create, edit, scale, redeploy, roll back and remove services; create secrets, configs and overlay networks. Each node also opens as a Docker host of its own, with its containers, logs, terminals, images and volumes. FleetOps asks you to type the name before a change that could stop its own service, its node or the agents.
Stacks deploy to a swarm as Swarm services, with the same editor, git sync, variables, secrets, revisions and rollback as on a Docker host, and the whole deploy: block. A deploy reports progress per service and fails on a paused update, a rejected task or a task left pending. A service changed outside its stack is marked as drifted, and the next plan lists what it puts back. Stacks deployed with docker stack deploy are listed too.
Swarm has its own rows in the role grid, and a grant can be limited to stacks, as a Kubernetes grant is limited to namespaces. A limited grant sees and changes only its stacks’ services, tasks, secrets, configs, networks and containers, on every page, feed and log; anything else reads as missing. For Enterprise licenses, a swarm counts its nodes. The Swarm guide has the details.
Builds
build works. A git stack builds its images from the repository: only the code under a service’s build context is sent, after .dockerignore. Any stack can use dockerfile_inline. Images are built on the target host before any container changes, and the deploy review shows what will be built. Each image is tagged from its context’s git tree, so a commit that changes only code redeploys just the services that build it. A rollback uses the images that revision built.
Secrets and configs
secrets and configs work. Put values in the stack’s Secrets tab, or take them from a stack variable or inline content. They are stored encrypted and copied into each container before it starts, so nothing is needed on the host. A secret is never shown again once saved, not even in the container’s Files tab. On a git stack, a config’s file is read from the repository at the same commit as the Compose file.
Git over SSH
A git stack can use an SSH URL, git@host:repo.git or ssh://…, with a deploy key that FleetOps generates for the stack or one you paste. SSH runs inside FleetOps, so the image needs no ssh program. Host keys are checked: GitHub, GitLab and Bitbucket against their published keys, other hosts trusted on the first sync. A changed key stops syncs until someone accepts it in the Git tab.
Limits
Submodules, Git LFS, and passphrase-protected or RSA SSH keys are not supported. A Swarm stack cannot use build, since Swarm cannot build: push the image to a registry. Swarm autolock is not supported.
Next
Port-forward, then API tokens, SIEM forwarding and long audit retention for Enterprise. See the roadmap.