Node components (kubelet, kube-proxy, container runtime) in Kubernetes - Step-by-Step Execution

Process Flow - Node components (kubelet, kube-proxy, container runtime)

Container Runtime

↓

Kubelet

↓

Pod & Container Management

↓

Kube-proxy

↓

Network Traffic Routing & Load Balancing

This flow shows how the container runtime runs containers, kubelet manages pods and containers on the node, and kube-proxy routes network traffic to the right pods.

Execution Sample

Kubernetes

1. Container Runtime pulls image and runs container
2. Kubelet monitors container status and reports to master
3. Kube-proxy updates network rules for service traffic

This sequence shows how node components work together to run containers and route traffic.

Process Table

Step	Component	Action	State Change	Output
1	Container Runtime	Pull image and start container	Container created and running	Container ID abc123 running
2	Kubelet	Check container status	Container status = Running	Status reported to master
3	Kubelet	Manage pod lifecycle	Pod containers monitored	Pod ready
4	Kube-proxy	Update network rules	Service IP routes to pod IP	Traffic routed correctly
5	Kube-proxy	Load balance traffic	Traffic distributed among pods	Requests balanced
6	Kubelet	Detect container failure	Container stopped	Restart container
7	Container Runtime	Restart container	Container running again	Container ID abc123 running
8	Kubelet	Report updated status	Status = Running	Master updated
9	Kube-proxy	Maintain network rules	Rules consistent	Traffic flows uninterrupted
10	System	Normal operation	All components healthy	Node ready

💡 Node components maintain container lifecycle and network routing continuously; no exit unless node shuts down.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 6	After Step 7	Final
Container Status	Not running	Running	Running	Running	Stopped	Running	Running
Pod Status	Not ready	Not ready	Ready	Ready	Ready	Ready	Ready
Network Rules	Empty	Empty	Updated	Updated	Updated	Updated	Updated

Key Moments - 3 Insights

Why does kubelet report container status to the master?

Kubelet reports container status (see step 2 and 8) so the master knows if pods are healthy and can schedule or reschedule workloads accordingly.

How does kube-proxy help with service traffic?

Kube-proxy updates network rules (step 4) to route traffic from service IPs to the correct pod IPs and load balances requests (step 5).

What happens if a container stops unexpectedly?

Kubelet detects failure (step 6) and instructs the container runtime to restart the container (step 7) to keep the pod running.

Visual Quiz - 3 Questions

Look at the execution table, what is the container status after step 6?

A Stopped

B Running

C Not running

D Unknown

💡 Hint

Check the 'Container Status' variable in variable_tracker after step 6.

At which step does kube-proxy update network rules for service traffic?

A Step 2

B Step 4

C Step 6

D Step 8

💡 Hint

Look at the 'Action' column in the execution_table for kube-proxy activities.

If the container runtime fails to restart the container at step 7, what would kubelet likely do next?

A Report container running

B Update network rules

C Report container stopped and retry restart

D Shutdown the node

💡 Hint

Refer to step 6 and 7 in execution_table and how kubelet handles container failure.

Concept Snapshot

Node components in Kubernetes:
- Container Runtime: pulls images, runs containers
- Kubelet: monitors containers, manages pod lifecycle, reports status
- Kube-proxy: manages network rules, routes and load balances service traffic
Together, they keep pods running and reachable on each node.

Full Transcript

In Kubernetes, each node runs key components to manage containers and network traffic. The container runtime pulls container images and runs them. The kubelet watches these containers, manages their lifecycle, and reports their status to the master node. The kube-proxy updates network rules to route service traffic to the right pods and balances load among them. If a container stops, kubelet detects this and asks the container runtime to restart it. This cycle keeps the node healthy and pods running smoothly.