GitOps, a term coined by WeaveWorks, is a way to do continuous delivery and manage your environments through git using pull requests.

Swarm-sync runs as a service in your Docker Swarm. It watches a Config Repo (a git repository managed by you) for changes and deploys them to your Swarm. Additionally it can watch Docker Registries for new images for your services and update you swarm Services accordingly.

The Config Repo contains a set of Swarm Packs and configuration values which will be used to set up your Swarm Services.

The best way to understand the Config Repo is by looking at the example Config Repo.

                 +---------+            +---------+            +-----------+
 @               |  Code   |            |         |            | Container |
-|-  +---------> |   Repo  +----------->+   CI    +----------->+  Registry |
/ \   commit     |         |   build    |         |   push     |           |
                 +---------+            +---------+            +-----------+
Developer                                                            |
                                                                     |
                                                                     |
                                                +--------------------+
                                                |
                                                |
                                                v
                  +---------+            +-----------+           +-----------+
 @                | Config  |            |  Swarm    |           |  Docker   |
-|-  +--------->  |   Repo  <----------->+    Sync   +----------->    Swarm  |
/ \   commit      |         |   sync     |           |   apply   |           |
                  +---------+            +-----------+           +-----------+              
Developer

There are 3 main components needed to achieve our GitOps pipeline:

1. Configuration Repository - a Git repository containing all the configuration for your Docker Swarm stacks. Example repository: kevb/swarm-pack-example

2. Container Registry - A Docker registry to push our application images to (hopefully from a CI somewhere else)

3. SwarmSync - SwarmSync will be running inside your Swarm as a service and will be configured to point to the other 2 components.

Swarm-Sync relies on Swarm Pack to compile and deploy services from templates. An understanding of swarm-pack is required to use swarm-sync, so if you haven't already take a look there.

1. Fork the repo https://github.com/swarm-pack/swarm-sync-example - this guide will use this URL, but you should replace with your own fork and re-configure your own desired config.

2. Create a config file for swarm-sync, similar to this one:

swarm-sync:

  # Stacks in target for this swarm-sync instance
  stacks:
    - nonprod

  # Update frequency for polling repo and image registry for changes (ms)
  # Below 1 minute not recommended
  updateInterval: 60000

  # Git details for your Swarm Configuration Repository
  git:
    url: https://github.com/swarm-pack/swarm-sync-example
    branch: master

  # Common config with swarm-pack
  docker:
    socketPath: /var/run/docker.sock
  repositories:
    - name: official
      url: https://github.com/swarm-pack/repository

Upload this file to a manager node in your Swarm

3. On the manager node, run

docker run -it \
 -v /var/run/docker.sock:/var/run/docker.sock \
 -v /path/to/swarm-sync.yml:/etc/swarm-sync.yml \
 kevbuk/swarm-sync --bootstrap

This uses the "--bootstrap" flag for swarm-sync, meaning it will not run as a daemon. That's because in our example config repo we have a swarm-pack configured for swarm-sync, so it will be deployed as a service. Make sure the swarm-sync config is the same inside your Config Repo values.

4. Check your desired services are now running on your Swarm

docker service ls

5. Push a change to your config repo, and check that the services update themselves within 5 minutes!

Stacks are a way to namespace things, and identify what is in scope for a particular instance of Swarm Sync.

For example, you might have 2 Swarms: prod and nonprod. One approach is to create corresponding Stacks in your config repo at stacks/prod and stacks/nonprod. Each Swarm has an instance of swarm-sync with different config files. In your prod Stack instance, you would have:

stacks:
  - prod

In your nonprod instance you'd have

stacks:
  - nonprod

With this configuration, the stack defined in stacks/nonprod/stack.yml will be synced to your nonprod Swarm and the stack defined in stacks/prod/stack.yml will be synced to your prod Swarm.

Config file should be mounted at /etc/swarm-sync.yml and Docker Config or Docker Secret is recommended for this.

If watching for image updates in a private docker registry, you will need to define authentication credentials.

This is done by mounting a docker secret matching the hostname of the registry at /run/secrets/registries/[hostname].

The secret should be a yml file in the following format:

username: xxx
password: xxx

For example, to authenticate docker.example.com, we mount the following secret to /run/secrets/registries/docker.example.com:

username: example
password: changeme

Node v11.9.0 Yarn v1.7.0

Install dependencies

yarn install

Start server development

yarn start:dev