update docs
parent
ee67a09af3
commit
813e186d91
|
@ -9,6 +9,20 @@ controller1 us-central1-f n1-standard-1 10.240.0.21 RUNNING
|
||||||
controller2 us-central1-f n1-standard-1 10.240.0.22 RUNNING
|
controller2 us-central1-f n1-standard-1 10.240.0.22 RUNNING
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Why
|
||||||
|
|
||||||
|
The Kubernetes components that make up the control plane include the following components:
|
||||||
|
|
||||||
|
* Kubernetes API Server
|
||||||
|
* Kubernetes Scheduler
|
||||||
|
* Kubernetes Controller Manager
|
||||||
|
|
||||||
|
Each component is being run on the same machines for the following reasons:
|
||||||
|
|
||||||
|
* The Scheduler and Controller Manager are tightly coupled with the API Server
|
||||||
|
* Only one Scheduler and Controller Manager can be active at a given time, but it's ok to run multiple at the same time. Each component will elect a leader via the API Server.
|
||||||
|
* Running multiple copies of each component is required for H/A
|
||||||
|
* Running each component next to the API Server eases configuration.
|
||||||
|
|
||||||
## Copy TLS Certs
|
## Copy TLS Certs
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue