vbatts/pkg
1
0
Fork 0
Code Pull requests Releases Activity
pkg/discovery
History
Daniel Hiltgen 125510e009 Add TLS support for discovery backend 
This leverages recent additions to libkv enabling client
authentication via TLS so the discovery back-end can be locked
down with mutual TLS.  Example usage:

    docker daemon [other args] \
        --cluster-advertise 192.168.122.168:2376 \
        --cluster-store etcd://192.168.122.168:2379 \
        --cluster-store-opt kv.cacertfile=/path/to/ca.pem \
        --cluster-store-opt kv.certfile=/path/to/cert.pem \
        --cluster-store-opt kv.keyfile=/path/to/key.pem

Signed-off-by: Daniel Hiltgen <daniel.hiltgen@docker.com>
2015-10-07 16:01:00 -07:00
..
file Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
kv Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
nodes Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
backends.go Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
discovery.go Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
discovery_test.go remove testify asserts from pkg/discovery 2015-10-02 13:05:15 -07:00
entry.go Add pkg/discovery for nodes discovery 2015-09-25 13:33:23 -07:00
generator.go Add pkg/discovery for nodes discovery 2015-09-25 13:33:23 -07:00
generator_test.go remove testify asserts from pkg/discovery 2015-10-02 13:05:15 -07:00
README.md Add pkg/discovery for nodes discovery 2015-09-25 13:33:23 -07:00

README.md

page_title page_description page_keywords
Docker discovery discovery docker, clustering, discovery

Discovery

Docker comes with multiple Discovery backends.

Backends

Using etcd

Point your Docker Engine instances to a common etcd instance. You can specify the address Docker uses to advertise the node using the --discovery-address flag.

$ docker daemon -H=<node_ip:2376> --discovery-address=<node_ip:2376> --discovery-backend etcd://<etcd_ip>/<path>

Using consul

Point your Docker Engine instances to a common Consul instance. You can specify the address Docker uses to advertise the node using the --discovery-address flag.

$ docker daemon -H=<node_ip:2376> --discovery-address=<node_ip:2376> --discovery-backend consul://<consul_ip>/<path>

Using zookeeper

Point your Docker Engine instances to a common Zookeeper instance. You can specify the address Docker uses to advertise the node using the --discovery-address flag.

$ docker daemon -H=<node_ip:2376> --discovery-address=<node_ip:2376> --discovery-backend zk://<zk_addr1>,<zk_addr2>>/<path>