install etcd on the controller nodes
parent
6a39adea4e
commit
b748f9d445
|
@ -9,7 +9,7 @@ In this lab you will bootstrap a 3 node etcd cluster. The following virtual mach
|
||||||
## Why
|
## Why
|
||||||
|
|
||||||
All Kubernetes components are stateless which greatly simplifies managing a Kubernetes cluster. All state is stored
|
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. etcd is being run on a dedicated set of machines for the
|
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:
|
following reasons:
|
||||||
|
|
||||||
* The etcd lifecycle is not tied to Kubernetes. We should be able to upgrade etcd independently of Kubernetes.
|
* The etcd lifecycle is not tied to Kubernetes. We should be able to upgrade etcd independently of Kubernetes.
|
||||||
|
|
Loading…
Reference in New Issue