Use Control Plane instead of Master (#18438)
* Use Control Plane instead of Master * improve image. The SVG was not matching the PNG, so I basically had to re-create it from scratch. I kept the visual similarities as mush as possible * remove tautological phrase * fix glossary references as well * improve cluster glossary to move from Master to Control Plane * improve english form
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
8f8bb5c2bf
commit
99ca9c0397
@@ -4,15 +4,15 @@ id: kube-scheduler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-scheduler/
|
||||
short_description: >
|
||||
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
||||
Control Plane component that watches for newly created pods with no assigned node, and selects a node for them to run on.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
---
|
||||
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
||||
Control Plane component that watches for newly created pods with no assigned node, and selects a node for them to run on.
|
||||
|
||||
<!--more-->
|
||||
|
||||
Factors taken into account for scheduling decisions include individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
|
||||
Factors taken into account for scheduling decisions include individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user