Remember the previous analogy about the Kubernetes control plane being like an air traffic control tower? Think of a worker node as an airport terminal where planes park and passengers board.

Think of a Worker Node as an Airport Terminal

This is to help ensure that the cluster is highly available and resilient to issues/outages.

Most Kubernetes clusters run with a minimum of three worker nodes.

The Kubelet is responsible for making sure that containers in a pod are running and healthy.The Kubelet communicates directly with the API server in the control plane.

The Kubelet is an agent that runs on every worker node.

The Container Runtime Interface (CRI) can create containers with the engines: <ul><li class="ql-align-justify">Containerd</li><li class="ql-align-justify">CRI-O</li><li class="ql-align-justify">Kata Containers</li><li class="ql-align-justify">AWS Firecracker</li></ul>

The container runtime enables the kublet to create containers locally.

It makes sure pods and services can communicate with other pods and services on nodes and in the control plane. Each kube-proxy communicates directly with the Kube-apiserver.

The kube proxy helps the worker node communicate with peers

<ul><li class="ql-align-justify">Kubelet</li><li class="ql-align-justify">Container Runtime</li><li class="ql-align-justify">Kube-proxy</li></ul>

Each worker node has three components

A brief walk-through of the Kubernetes worker node architecture.

Think of a Worker Node as an Airport Terminal

Similar ideas to Think of a Worker Node as an Airport Terminal

The Basics Of Conversation

How to study 📚🦋💻📑

Get organized

Pay attention in class