Keyboard Shortcuts N Next post
P Previous post
S Save / unsave
R Read aloud
T Toggle theme
/ Focus search
Esc Close panels
🔥
Ready to read...
Architecture K8s Basics Kubernetes Kubernetes: From Zero to Production Module 1 - Kubernetes Fundamentals

Kubernetes Architecture - Control Plane and Worker Nodes

Reviewed & accurate
AI Summary

What You Will Learn

Intermediate

  • The control plane components
  • Worker node components
  • How they communicate
Kubernetes Cluster ArchitectureControl Plane (Master Node)API ServerEntry pointSchedulerAssigns podsControllerReconciliationetcdKey-value storeWorker Node 1Pod APod Bkubelet + kube-proxyWorker Node 2Pod CPod Dkubelet + kube-proxyWorker Node 3Pod EPod Fkubelet + kube-proxy
Kubernetes cluster: Control Plane manages Worker Nodes, which run Pods

Control Plane (Master Node)

The control plane makes global decisions and manages the cluster. It has 4 components:

ComponentWhat it does
API ServerEntry point for all K8s commands (kubectl talks to this)
etcdKey-value store - the brain of the cluster (stores all state)
SchedulerDecides which node runs each Pod
Controller ManagerRuns reconciliation loops (keeps desired state = actual state)

Worker Nodes

Worker nodes run your application Pods. Each node has 3 components:

ComponentWhat it does
kubeletAgent that manages Pods on the node. Talks to API server.
kube-proxyManages network rules and load balancing
Container RuntimeRuns containers (containerd, CRI-O, Docker)
How they communicate
kubectl -> API Server -> etcd (stores state) -> Scheduler (assigns Pods) -> kubelet (on worker node runs the Pod) -> container runtime (runs containers).

Practical Exercise

Run: kubectl get nodes - see your worker node
Run: kubectl cluster-info - see control plane URL
Run: minikube ssh - SSH into the node
Inside: docker ps - see K8s components running as containers

Key Takeaways

  • Control Plane: API Server, etcd, Scheduler, Controller Manager.
  • Worker Nodes: kubelet, kube-proxy, container runtime.
  • API Server is the entry point - all commands go through it.
  • etcd stores ALL cluster state (the source of truth).
  • Scheduler decides which node runs each Pod.
Previously: Lesson 04 installed K8s.
Today: You learned: How a Kubernetes cluster is structured.
Next: Lesson 06 covers the declarative model.
Test Your Knowledge
How did you find this?

Comments

Join the discussion! Sign in with your Google or Blogger account, or comment as Anonymous - no account needed. For quick questions, also reach me on Telegram @cytestch.

Comments