A control plane is the brain of a Kubernetes cluster: it controls worker resources and provides one Kubernetes API for deploying applications across the cluster. Worker nodes run the applications; control plane nodes manage them. section 1.2.1
The control plane coordinates the cluster through several components:
- The Kubernetes API Server exposes the RESTful API through which engineers and other components create objects. section 1.2.3
- etcd persists objects created through the API; the API Server is the only component that communicates with it. section 1.2.3
- The Scheduler selects a worker node for each application instance. section 1.2.3
- Controllers bring API-created objects to life, sometimes communicating with external systems such as a cloud provider. section 1.2.3
Control plane components hold and control cluster state but do not run applications. They can run on one node in a non-production cluster or be replicated across multiple nodes for high availability; highly available clusters use at least three physical control plane nodes. section 1.2.1 section 1.2.3
Figure 1.12 The components of the Kubernetes control plane
Use the control-plane component diagram to connect the API Server, etcd, Scheduler, and controllers with their cluster-management roles. section 1.2.3







