Kubernetes Control Plane Diagram

Kubernetes Control Plane and Worker Nodes

This Kubernetes architecture diagram separates the control plane from the worker nodes. The API server is the central control-plane interface. It communicates with etcd for cluster state, with the scheduler for placement decisions, and with the controller manager for reconciliation. The API server also communicates with two worker nodes through their kubelets. Each worker node runs application pods. The diagram is intentionally high-level, making it suitable for onboarding or documentation. Add networking, ingress, storage classes, or an external control-plane endpoint when those parts matter to the design. Keep the diagram current when equipment, cable paths, service ownership, or security boundaries change, so it remains useful for planning and operations.

Type Network topologyStandard Cisco-convention topology iconsEngine schematex-networkUpdated 9/24/2026

The request

“A Kubernetes cluster with an API server connected to etcd, the scheduler, controller manager, and two worker nodes; each worker node runs application pods.”

Then tryAdd a kube-proxy on each worker nodeAdd a third worker node

What is in this drawing