From a759be0db39649ff8473d3841d572672b86835b2 Mon Sep 17 00:00:00 2001 From: Justin Santa Barbara Date: Sat, 21 Jan 2017 13:28:14 -0500 Subject: [PATCH] More nuance in etcd isolation recommendation Clarify that while running etcd on a separate set of machine is a good idea, it isn't tested. --- docs/03-etcd.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/03-etcd.md b/docs/03-etcd.md index 60ab554..1321992 100644 --- a/docs/03-etcd.md +++ b/docs/03-etcd.md @@ -9,13 +9,14 @@ In this lab you will bootstrap a 3 node etcd cluster. The following virtual mach ## Why All Kubernetes components are stateless which greatly simplifies managing a Kubernetes cluster. All state is stored -in etcd, which is a database and must be treated specially. To limit the number of compute resource to complete this lab etcd is being installed on the Kubernetes controller nodes. In production environments etcd should be run on a dedicated set of machines for the -following reasons: +in etcd, which is a database and must be treated specially. To limit the number of compute resource to complete this lab etcd is being installed on the Kubernetes controller nodes, although some people will prefer to run etcd on a dedicated set of machines for the following reasons: * The etcd lifecycle is not tied to Kubernetes. We should be able to upgrade etcd independently of Kubernetes. * Scaling out etcd is different than scaling out the Kubernetes Control Plane. * Prevent other applications from taking up resources (CPU, Memory, I/O) required by etcd. +However, all the e2e tested configurations currently run etcd on the master nodes. + ## Provision the etcd Cluster Run the following commands on `controller0`, `controller1`, `controller2`: