Kubernetes is an open source container management tool that you can use to deploy, monitor, and maintain containers. Kubernetes refers to the master node as well as worker nodes. You can create separate instances of both master and worker nodes in your Kubernetes cluster to support your organisation’s needs. We will see how Kubernetes works with Master Node and Worker Node. In this article, we will explain each component in detail and see how they work together.
What is Kubernetes Master Node? #
The master node is the Kubernetes control plane. It’s the brain of the system. It is responsible for managing the other components — the worker nodes. Kubernetes master nodes are responsible for all cluster-level tasks. These tasks include deploying new pods and scheduling containers across the worker nodes.
What is Kubernetes Worker Node? #
The worker node is the Kubernetes compute node. It is responsible for running the containers you schedule. Kubernetes worker nodes are responsible for running containers scheduled by the master node. Node types are the Kubernetes resource types you use to specify the amount of resources a worker node requires to run. Node types help you scale your cluster, and you can use them when you have different types of workloads in your cluster.
Kubernetes Components #
Master Node – The master node is the control plane of the cluster, responsible for managing and scheduling tasks across the worker nodes.
Worker Node – The worker nodes are responsible for running workloads as scheduled by the master node.
Kubelet – Each worker node is responsible for running pods. The kubelet is a component running on each worker node that facilitates communication between pods and the node. In a Kubernetes cluster, the kubelet is responsible for reading the pod definition and ensuring that the container running the pod is healthy.
Kube-proxy – This proxy runs on each worker node and routes traffic to pods in the cluster.
Container Runtime – Kubernetes uses a container runtime such as Docker to run containers. The container runtime schedules containers on worker nodes and is responsible for pulling the container image from the Docker registry.
How does Kubernetes Master Node work? #
The master node is responsible for managing the cluster and scheduling tasks across the worker nodes.
Initialisation – When you start the Kubernetes master node, it creates a kube-apiserver process. The kube-apiserver process is responsible for managing the cluster by implementing the Kubernetes API.
Deployment – The kube-apiserver process is responsible for scheduling and deploying new containers. This process is responsible for reading the Pod definition and matching it against the containers available in the cluster.
Health Check – The kube-apiserver process is responsible for scheduling tasks across the worker nodes. The master node also listens for heartbeat messages from the worker nodes to ensure that they are running. If a worker node doesn’t respond to a heartbeat message, the master node restarts the worker node.
How does Kubernetes Worker Node work? #
The worker node is responsible for running the containers. The Kubernetes master node schedules the containers across the worker nodes. When you start a Kubernetes worker node, it creates a kubelet process. The kubelet process is responsible for reading the Pod definition and running the containers. The worker node also starts a kube-proxy process to handle network routing. When you create a container, you use a container image. The worker node pulls the container image from the Docker registry. It then schedules the container on the worker node.
Key takeaways #
Kubernetes is an open source container management tool that you can use to deploy, monitor, and maintain containers. The master node is the control plane of the cluster and is responsible for managing and scheduling tasks across the worker nodes. The worker nodes are responsible for running workloads as scheduled by the master node. The kube-apiserver process is responsible for managing the cluster and implementing the Kubernetes API. The kubelet process on each worker node is responsible for reading the Pod definition and running the containers. The kubelet process also listens for heartbeat messages from the worker nodes to ensure that they are running.
Get your employees up-to-date with online courses and certifications in web tech, software development, and IT from London School of Emerging Technology.
