github.com/greenboxal/deis@v1.12.1/docs/managing_deis/isolating-etcd.rst (about) 1 :title: Isolating etcd 2 :description: Configuring the cluster to isolate etcd 3 4 .. _isolating-etcd: 5 6 Isolating etcd 7 ============== 8 9 .. include:: ../_includes/_isolating-etcd-description.rst 10 11 .. note:: 12 13 The approach documented here works as of Deis 1.9. Older versions of Deis 14 utilize an older version of etcd that did not include the proxy 15 functionality. 16 17 cloud-config 18 ------------ 19 20 To realize the topology described above, it is necessary, at the time of 21 provisioning, to provide different `cloud-config`_ for those hosts that will run 22 etcd and for those that will only run an etcd proxy. 23 24 .. _`cloud-config`: ../../contrib/coreos/user-data.example 25 26 For the small, fixed number of hosts running full etcd and satisfying the 27 "central services" role (as described in the CoreOS documentation), the 28 cloud-config provided with Deis is sufficient. 29 30 For hosts running only an etcd proxy, satisfying the "worker" role (as described 31 in the CoreOS documentation), cloud-config must be tweaked slightly to include 32 the ``-proxy on`` flag. For example: 33 34 .. code-block:: yaml 35 36 #cloud-config 37 38 coreos: 39 etcd2: 40 discovery: <discovery URL here> 41 proxy: on 42 # ... 43 44 Isolating etcd as described here requires subsets of a cluster's hosts to be 45 configured differently from one another (including or excluding the 46 ``-proxy on`` flag). Deis provisioning scripts do not currently account for 47 this, so managing separate cloud-config for each subset of nodes in the cluster 48 is left as an exercise for the advanced operator.