Kubernetes ยท Architecture map
The control plane and a worker node Use this map to locate each component. The two motion diagrams explain the actions and customer traffic separately.
Kubernetes cluster architecture Clients, controllers, the scheduler, and the kubelet exchange state through the API server, which stores it in etcd; the kubelet coordinates a runtime to run application containers. Management: client + control plane One worker node: run the application kubectl / clients Submit changes. Read cluster status. API server Check API requests. Read/write cluster state. etcd Store Kubernetes state. Used by the API server. Controllers Watch and reconcile. Create/update objects. Scheduler Choose suitable nodes. Record Pod assignments. kubelet Watch assigned Pods. Coordinate local startup. Container runtime Pull images. Start/stop containers. Application Pods Run the shop containers. Serve application traffic. Kubelet coordinates the runtime. The runtime starts containers in Pods. Two-ended lines: API/state exchanges. One-way lines: local startup actions. Networking and storage support the worker. Simplified map: one worker is shown; clusters may have many. API conversations do not represent customer web traffic. The API server and etcd do not run every request through the scheduler.