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

Merge pull request #20424 from Fale/concept-overview-components

Browse Source 
control plane should not be capitalized
This commit is contained in:
Kubernetes Prow Robot
2020-04-18 09:49:36 -07:00
committed by GitHub
parent 47f3785d69 f477fd8d37
commit ccd4710ad2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/overview/components.md
+3 -3
View File
@@ -25,10 +25,10 @@ Here's the diagram of a Kubernetes cluster with all the components tied together
{{% capture body %}} {{% capture body %}}
## Control Plane Components ## Control Plane Components
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). 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).
Control Plane components can be run on any machine in the cluster. However, 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 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 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. [Building High-Availability Clusters](/docs/admin/high-availability/) for an example multi-master-VM setup.