I'm currently a 2nd-year B.Sc. student specializing in Cloud Computing. After getting comfortable with Docker and Ansible, today I started learning Kubernetes Architecture.
Here are my notes on the "Brain" vs. the "Body" of a K8s cluster.
The Control Plane (Master Node) 🧠
The Control Plane is responsible for maintaining the desired state of the cluster.
API Server (kube-apiserver): The entry point for all REST commands. It’s the only component that communicates directly with etcd.
etcd: A consistent and highly-available key value store used as Kubernetes' backing store for all cluster data.
Scheduler (kube-scheduler): Watches for new Pods and assigns them to nodes based on resource availability (CPU/RAM).
Controller Manager: Runs controller processes (e.g., Node Controller) to monitor the cluster state.
The Data Plane (Worker Nodes) 💪
This is where our application workloads run.
Kubelet: An agent that runs on each node. It ensures that containers are running in a Pod.
Kube-proxy: Handles networking. It maintains network rules on nodes to allow communication across the cluster.
Container Runtime: The underlying software (like Docker/containerd) that runs the containers.
Why this matters?
Understanding that the Scheduler decides where a pod goes, but the Kubelet is what actually starts it, helps clarify the chain of command.
I'll be posting more updates as I move on to Pods, Deployments, and Services.
Linkedin: https://www.linkedin.com/in/dasari-jayanth-b32ab9367/
Top comments (0)