Deploys a consul cluster as containers.
- Deploys a consul cluster of servers and clients.
- Resolves DNS queries on the host machine for .consul domains. Falls back to public DNS servers by default.
- Resolves DNS queries from within docker containers (specify
--dns=172.17.0.1) See below. - Tested on a 5 node DigitalOcean cluster using Molecule and Testinfra.
- The gossip communication between instances in unencrypted. The HTTP endpoints are unencrypted. This is only suitable for deployment within private networks.
The deployment requires the docker daemon to be installed on each host since Consul runs as a container.
The role will deploy server agents to any node inside the consul_server group
and otherwise deploy a client to the remaining nodes. It is required that
you specify at least 3 server nodes for high availablilty.
Refer to the Consul architecture docs for a better overview.
---
all:
children:
web:
hosts:
web01:
ansible_host: 172.16.142.101
web02:
ansible_host: 172.16.142.102
db:
hosts:
db01:
ansible_host: 172.16.142.103
cache:
hosts:
cache01:
ansible_host: 172.16.142.104
consul_server:
hosts:
web02:
db01:
cache01:Using the playbook below we will deploy a Consul server instance to web02,
db01, cache01. Consul client will be deployed to the rest.
You have to specify what IP range consul will be listening on (most likely
your cloud private network). Consul will then find largest IP address listening
on that network range ansible_all_ipv4_addresses | ipaddr(consul_network_range) | max.
---
- name: Deploy consul
hosts: all
tasks:
- name: Deploy consul
import_role:
name: ansible-role-consul
vars:
consul_network_range: '172.16.142.0/24'Specify the DNS server as the host IP when starting the container
docker run --dns 172.17.0.1 curlimages/curl "http://echo.service.consul:13000"