Add master term and expand control plane

Signed-off-by: Davi Garcia <dvercill@redhat.com>
This commit is contained in:
Davi Garcia
2020-04-16 11:13:35 -03:00
parent f2839de743
commit c0f60fa4f7
2 changed files with 27 additions and 0 deletions
@@ -11,3 +11,15 @@ tags:
- fundamental
---
The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
<!--more-->
This layer is composed by many different components, such as (but not restricted to):
* {{< glossary_tooltip text="etcd" term_id="etcd" >}}
* {{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}
* {{< glossary_tooltip text="Scheduler" term_id="kube-scheduler" >}}
* {{< glossary_tooltip text="Controller Manager" term_id="kube-controller-manager" >}}
* {{< glossary_tooltip text="Cloud Controller Manager" term_id="cloud-controller-manager" >}}
These components can be run as traditional operating system services (daemons) or as containers. The hosts running these components were historically called {{< glossary_tooltip text="masters" term_id="master" >}}.