mirrors
/
kubernetes-the-hard-way
mirror of https://github.com/kelseyhightower/kubernetes-the-hard-way
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

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.
pull/101/merge
Justin Santa Barbara 2017-01-21 13:28:14 -05:00 committed by Kelsey Hightower
parent cb6564a013
commit a759be0db3
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/03-etcd.md
View File

@ -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`: