Kubernetes architecture (control plane and nodes) - Step-by-Step Execution

Process Flow - Kubernetes architecture (control plane and nodes)

User/Client

↓

API Server

↓

Controller Manager

↓

etcd (Data Store)

↓

Kubelet

↓

Container Runtime

The control plane manages the cluster state and schedules work. Nodes run the actual containers. Communication flows from user to API server, then to scheduler and controllers, and finally to nodes.

Execution Sample

Kubernetes

# Control Plane Components
kubectl get componentstatuses

# Node Components
kubectl get nodes
kubectl describe node <node-name>

Commands to check the health of control plane components and view node details.

Process Table

Step	Component	Action	Input	Output/Effect
1	User/Client	Sends request	kubectl apply -f pod.yaml	Request received by API Server
2	API Server	Validates and processes	Pod spec from user	Stores desired state in etcd
3	Scheduler	Watches API Server	New pod without node assignment	Assigns pod to a suitable node
4	Controller Manager	Monitors cluster state	Pod assigned to node	Ensures pod is running, creates replicas if needed
5	etcd	Stores cluster state	Desired and current states	Persistent data storage for cluster
6	Kubelet (Node)	Receives pod assignment	Pod spec from API Server	Starts containers via container runtime
7	Container Runtime	Runs containers	Container images and commands	Containers running inside pods
8	User/Client	Checks status	kubectl get pods	Shows pod running status
9	Exit	No more actions	All pods scheduled and running	Cluster stable and operational

💡 All pods are scheduled and running; cluster state matches desired state.

Status Tracker

Component	Initial State	After Step 2	After Step 3	After Step 6	Final State
API Server	Idle	Received pod spec	Pod scheduled	Pod spec sent to node	Processed requests
Scheduler	Idle	No pod to schedule	Assigned pod to node	Waiting for next pod	Ready for next scheduling
Controller Manager	Idle	No action	Monitors pod state	Ensures pod running	Maintains desired replicas
Kubelet	Idle	No pod assigned	Waiting for pod	Starts container	Pod running
etcd	Stores cluster data	Updated desired state	Updated with node assignment	Updated with pod status	Persistent cluster state

Key Moments - 3 Insights

Why does the Scheduler assign pods after the API Server stores the pod spec?

Because the Scheduler watches the API Server for new pods without node assignments (see execution_table step 3). It needs the pod spec stored first to decide where to place the pod.

How does the Kubelet know what containers to run?

The Kubelet receives the pod spec from the API Server after scheduling (step 6). It uses this spec to start containers via the container runtime.

What role does etcd play in the cluster?

etcd stores the desired and current cluster state persistently (step 5). It acts as the single source of truth for the cluster.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What does the Scheduler do?

A Starts the container runtime

B Stores the pod spec in etcd

C Assigns the pod to a suitable node

D Validates the pod spec

💡 Hint

Refer to execution_table row with Step 3 under 'Action' and 'Output/Effect'

At which step does the Kubelet start containers on a node?

A Step 2

B Step 6

C Step 4

D Step 8

💡 Hint

Check execution_table row with Step 6 for Kubelet actions

If the etcd component fails, what is the likely impact?

A Cluster state cannot be stored or retrieved

B Pods will not be scheduled

C Containers will not start on nodes

D User requests will be ignored

💡 Hint

Look at the role of etcd in execution_table step 5 and variable_tracker

Concept Snapshot

Kubernetes architecture has two main parts:
- Control Plane: API Server, Scheduler, Controller Manager, etcd store cluster state and manage scheduling.
- Nodes: Run Kubelet and container runtime to run pods.
User requests go to API Server, which stores desired state in etcd.
Scheduler assigns pods to nodes.
Kubelet runs containers as per pod specs.

Full Transcript

Kubernetes architecture consists of a control plane and worker nodes. The control plane includes the API Server, Scheduler, Controller Manager, and etcd. Users send commands to the API Server, which validates and stores the desired state in etcd. The Scheduler watches for new pods and assigns them to nodes. The Controller Manager ensures the cluster state matches the desired state. Worker nodes run the Kubelet, which receives pod specs and starts containers using the container runtime. etcd stores all cluster data persistently. This flow ensures the cluster runs as expected with pods scheduled and containers running on nodes.