whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use Control Plane instead of Master (#18438)

Browse Source 
* 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:
Fabio Alessandro Locati
2020-01-16 14:24:22 +01:00
committed by Kubernetes Prow Robot
parent 8f8bb5c2bf
commit 99ca9c0397
6 changed files with 786 additions and 1338 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/overview/components.md
+5 -6
View File
@@ -11,7 +11,7 @@ card:
{{% capture overview %}}
When you deploy Kubernetes, you get a cluster.
{{< glossary_definition term_id="cluster" length="all" prepend="A cluster is">}}
{{< glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}}
This document outlines the various components you need to have
a complete and working Kubernetes cluster.
@@ -23,13 +23,12 @@ Here's the diagram of a Kubernetes cluster with all the components tied together
{{% /capture %}}
{{% capture body %}}
## Master Components
## Control Plane Components
Master components provide the cluster's control plane. Master components make global decisions about the
cluster (for example, scheduling), and they detect and respond to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied).
The Control Plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied).
Master components can be run on any machine in the cluster. However,
for simplicity, set up scripts typically start all master components on
Control Plane components can be run on any machine in the cluster. However,
for simplicity, set up scripts typically start all Control Plane components on
the same machine, and do not run user containers on this machine. See
[Building High-Availability Clusters](/docs/admin/high-availability/) for an example multi-master-VM setup.