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

Add kube-apiserver, kube-controller-manager, kube-scheduler and etcd to glossary. (#6600)

Browse Source 
* Move master component definitions to glossary

* review comments

* Update controller.yaml

Making a trivial change to un-stuck Travis

* Update controller.yaml

Removing trivial change
This commit is contained in:
Tina Zhang
2018-01-25 22:34:06 +00:00
committed by Zach Corleissen
parent 1d6f7b9d55
commit 3c50ce9d87
7 changed files with 70 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/overview/components.md
+7 -9
View File
@@ -22,16 +22,19 @@ the same VM, and do not run user containers on this VM. See
### kube-apiserver
[kube-apiserver](/docs/admin/kube-apiserver/) exposes the Kubernetes API. It is the front-end for the
Kubernetes control plane. It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).
{% glossary_definition term_id="kube-apiserver" length="all" %}
### etcd
[etcd](/docs/tasks/administer-cluster/configure-upgrade-etcd/) is used as Kubernetes' backing store. All cluster data is stored here. Always have a backup plan for etcd's data for your Kubernetes cluster.
{% glossary_definition term_id="etcd" length="all" %}
### kube-scheduler
{% glossary_definition term_id="kube-scheduler" length="all" %}
### kube-controller-manager
[kube-controller-manager](/docs/admin/kube-controller-manager/) runs controllers, which are the background threads that handle routine tasks in the cluster. Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.
{% glossary_definition term_id="kube-controller-manager" length="all" %}
These controllers include:
@@ -56,11 +59,6 @@ The following controllers have cloud provider dependencies:
* Service Controller: For creating, updating and deleting cloud provider load balancers
* Volume Controller: For creating, attaching, and mounting volumes, and interacting with the cloud provider to orchestrate volumes
### kube-scheduler
[kube-scheduler](/docs/admin/kube-scheduler/) watches newly created pods that
are not assigned to any node, and selects a node for them to run on.
### addons
Addons are pods and services that implement cluster features. The pods may be managed