Skip to content

Commit 558f36c

Browse files
authored
Merge pull request #28720 from anubha-v-ardhan/patch-2
Replace ha-master-gce.png with SVG
2 parents b41e88b + c9568cb commit 558f36c

File tree

2 files changed

+13
-2
lines changed

2 files changed

+13
-2
lines changed

content/en/docs/images/ha-control-plane.svg

Lines changed: 4 additions & 0 deletions
Loading

content/en/docs/tasks/administer-cluster/highly-available-control-plane.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,10 +133,18 @@ the [etcd administration guide](https://etcd.io/docs/v2.3/admin_guide/#member-mi
133133

134134
## Implementation notes
135135

136-
![ha-master-gce](/images/docs/ha-master-gce.png)
136+
![ha-control-plane](/docs/images/ha-control-plane.svg)
137137

138138
### Overview
139+
The figure above illustrates three control plane nodes and their components in a highly available cluster. The control plane node’s components employ the following methods:
139140

141+
- etcd: instances are clustered together using consensus.
142+
143+
- Controllers, scheduler and cluster auto-scaler: only one instance of each will be active in a cluster using a lease mechanism.
144+
145+
- Add-on manager: each works independently to keep add-ons in sync.
146+
147+
In addition, a load balancer operating in front of the API servers routes external and internal traffic to the control plane nodes.
140148
Each of the control plane nodes will run the following components in the following mode:
141149

142150
* etcd instance: all instances will be clustered together using consensus;
@@ -215,4 +223,3 @@ server coordination (for example, the `StorageVersionAPI` feature gate).
215223

216224
[Automated HA master deployment - design doc](https://git.k8s.io/community/contributors/design-proposals/cluster-lifecycle/ha_master.md)
217225

218-

0 commit comments

Comments
 (0)