Course contentsShow
← Cloud and Infrastructure
Lesson 1108 of 2,98922. Kubernetes ArchitectureFree lesson

Worker Node Components Introduction

Overview of the components that run on every worker node in the cluster.

Worker Node Components Introduction

What you'll learn: You'll discover the essential software components that must run on every worker node to enable it to host and manage containerized applications in Kubernetes.

What is a Worker Node?

In Kubernetes, worker nodes are the machines (physical or virtual) where your applications actually run. While the control plane makes decisions about the cluster, worker nodes do the actual work of running containers. Think of the control plane as a construction company's headquarters, and worker nodes as the actual construction sites where buildings go up.

Core Components on Every Worker Node

Every worker node runs three critical components that work together:

  1. kubelet - The node's primary agent that communicates with the API server, receives Pod specifications, and ensures containers are running as expected
  2. kube-proxy - Manages network rules on the node, enabling communication between Pods and external traffic
  3. Container runtime - The software responsible for actually running containers (like Docker, containerd, or CRI-O)

How They Work Together

When the control plane decides a Pod should run on a specific node, the kubelet on that node receives the instructions. It then tells the container runtime to pull images and start containers. Meanwhile, kube-proxy configures networking so the Pod can communicate with other Pods and receive traffic from services.

It's like a factory floor: kubelet is the floor manager receiving orders from headquarters, the container runtime is the machinery doing the actual production work, and kube-proxy is the logistics team ensuring materials (network traffic) flow correctly.

Key Takeaway: Every Kubernetes worker node runs kubelet (node agent), kube-proxy (network manager), and a container runtime—these three components transform the node into a functioning member of the cluster capable of running containerized workloads.