mirror of https://github.com/docker/docs.git
This adds TLS support into the KV store for swarm. The manage, join,
and list commands all have a new CLI argument, matching the docker engine
discovery backend. This required adding the tlsconfig utility
package from docker engine.
Here's an example showing re-use of the cluster certs for the KV store:
swarm manage --tlsverify \
--tlscacert /etc/docker/ssl/ca.pem
--tlscert /etc/docker/ssl/cert.pem
--tlskey /etc/docker/ssl/key.pem
--discovery-opt kv.cacertfile=/etc/docker/ssl/ca.pem
--discovery-opt kv.certfile=/etc/docker/ssl/cert.pem
--discovery-opt kv.keyfile=/etc/docker/ssl/key.pem
--advertise 192.168.122.47:3376
etcd://192.168.122.47:2379
Signed-off-by: Daniel Hiltgen <daniel.hiltgen@docker.com>
|
||
|---|---|---|
| .. | ||
| README.md | ||
| token.go | ||
| token_test.go | ||
README.md
#discovery.hub.docker.com
Docker Swarm comes with a simple discovery service built into the Docker Hub
#####Create a new cluster
-> POST https://discovery.hub.docker.com/v1/clusters
<- <token>
#####Add new nodes to a cluster
-> POST https://discovery.hub.docker.com/v1/clusters/<token>?ttl=<ttl> Request body: "<ip>:<port1>"
<- OK
-> POST https://discovery.hub.docker.com/v1/clusters/<token>?ttl=<ttl> Request body: "<ip>:<port2>")
<- OK
#####List nodes in a cluster
-> GET https://discovery.hub.docker.com/v1/clusters/<token>
<- ["<ip>:<port1>", "<ip>:<port2>"]
#####Delete a cluster (all the nodes in a cluster)
-> DELETE https://discovery.hub.docker.com/v1/clusters/<token>
<- OK