From d72d54be599240ef4e107ce1b084e7cd43104657 Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Thu, 16 Apr 2015 12:02:37 -0700 Subject: [PATCH] docs: add info about discovery size parameter --- Documentation/cloud-config.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/cloud-config.md b/Documentation/cloud-config.md index 9e92242..1a85abe 100644 --- a/Documentation/cloud-config.md +++ b/Documentation/cloud-config.md @@ -76,14 +76,16 @@ _Note: The `$private_ipv4` and `$public_ipv4` substitution variables referenced #### etcd2 The `coreos.etcd2.*` parameters will be translated to a partial systemd unit acting as an etcd configuration file. -If the platform environment supports the templating feature of coreos-cloudinit it is possible to automate etcd configuration with the `$private_ipv4` and `$public_ipv4` fields. For example, the following cloud-config document... +If the platform environment supports the templating feature of coreos-cloudinit it is possible to automate etcd configuration with the `$private_ipv4` and `$public_ipv4` fields. When generating a [discovery token](https://discovery.etcd.io/new?size=3), set the `size` parameter, since etcd uses this to determine if all members have joined the cluster. After the cluster is bootstrapped, it can grow or shrink from this configured size. + +For example, the following cloud-config document... ```yaml #cloud-config coreos: etcd2: - # generate a new token for each unique cluster from https://discovery.etcd.io/new + # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3 discovery: https://discovery.etcd.io/ # multi-region and multi-cloud deployments need to use $public_ipv4 advertise-client-urls: http://$public_ipv4:2379