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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Kubernetes cluster overview
Key decisions
- Cluster state: etcd stores the control-plane state.
- Scheduling: The scheduler assigns pods to workers.
- Workloads: Worker nodes run the application pods.
When to reuse this
Use this to introduce the Kubernetes control plane and the relationship between workers and pods.
Frequently asked questions
What is the Kubernetes control plane?
What does etcd store?
What runs application pods?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.