Update content/en/docs/tasks/administer-cluster/highly-available-control-plane.md
Co-authored-by: chrismetz09 <cymetz@gmail.com>
This commit is contained in:
		
							parent
							
								
									6cb9177e2b
								
							
						
					
					
						commit
						436d3fe8c4
					
				|  | @ -136,7 +136,15 @@ the [etcd administration guide](https://etcd.io/docs/v2.3/admin_guide/#member-mi | ||||||
|  |  | ||||||
| 
 | 
 | ||||||
| ### Overview | ### Overview | ||||||
|  | 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: | ||||||
| 
 | 
 | ||||||
|  | - etcd: instances are clustered together using consensus. | ||||||
|  | 
 | ||||||
|  | - Controllers, scheduler and cluster auto-scaler: only one instance of each will be active in a cluster using a lease mechanism. | ||||||
|  | 
 | ||||||
|  | - Add-on manager: each works independently to keep add-ons in sync. | ||||||
|  | 
 | ||||||
|  | In addition, a load balancer operating in front of the API servers routes external and internal traffic to the control plane nodes. | ||||||
| Each of the control plane nodes will run the following components in the following mode: | Each of the control plane nodes will run the following components in the following mode: | ||||||
| 
 | 
 | ||||||
| * etcd instance: all instances will be clustered together using consensus; | * etcd instance: all instances will be clustered together using consensus; | ||||||
|  | @ -215,4 +223,3 @@ server coordination (for example, the `StorageVersionAPI` feature gate). | ||||||
| 
 | 
 | ||||||
| [Automated HA master deployment - design doc](https://git.k8s.io/community/contributors/design-proposals/cluster-lifecycle/ha_master.md) | [Automated HA master deployment - design doc](https://git.k8s.io/community/contributors/design-proposals/cluster-lifecycle/ha_master.md) | ||||||
| 
 | 
 | ||||||
| 
 |  | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue