In a Kubernetes cluster, there are two main types of nodes: master nodes and worker nodes. Each node has a specific role and performs different functions to ensure the proper functioning of the cluster. Let's dive into a detailed understanding of these roles.
Master nodes are responsible for managing the entire Kubernetes cluster. They act as the centralized control plane and oversee the cluster's operations. Some of the key components and functions performed by master nodes include:
API Server: The API server acts as a communication interface between various components of the cluster and the external API clients. It handles requests and manages resources within the cluster.
Scheduler: The scheduler is responsible for assigning workloads to suitable worker nodes based on various factors like resource availability, policies, and constraints.
etcd: An essential component of the master node cluster, etcd is a distributed key-value store that stores the cluster's configuration data and state.
Controller Manager: The controller manager monitors the cluster's desired state and takes necessary actions to bring the current state closer to the desired state. It manages various controllers responsible for tasks like replication, endpoint creation, and namespace creation.
Master nodes handle cluster-wide operations like managing and enforcing policies, maintaining a consistent and desired state of the cluster, and carrying out automatic healing and scaling of applications.
To ensure high availability of the master nodes themselves, it is common to set up multiple master nodes in a cluster. These master nodes communicate with each other and elect a leader to coordinate and perform the necessary tasks. This way, if one master node fails, another one can take over and continue managing the cluster.
Worker nodes, also known as minion nodes, are the workhorses of the Kubernetes cluster. Their primary responsibility is to run the actual workloads as containers. Key components and functions of the worker nodes include:
Worker nodes are equipped with container runtime environments, such as Docker or containerd, which enable them to run containers. These container runtimes pull container images, create containers, manage their lifecycle, and provide isolation between multiple running containers.
Kubelet is an agent that runs on each worker node and communicates with the master node. It ensures the containers on its node are running and healthy, and reports their status back to the master node.
Worker nodes also run a network proxy, which enables communication between different pods residing on different worker nodes. This ensures that services can discover and reach each other within the cluster.
Worker nodes are responsible for executing pods, which are the smallest deployable units in Kubernetes. Each pod consists of one or more containers, and it is the worker node's responsibility to spin up the necessary containers based on the pod specifications.
Worker nodes provide resource isolation, ensuring that each pod and container only consume their allocated resources. This prevents any single pod or container from monopolizing the entire cluster's resources.
Understanding the roles of master and worker nodes is crucial for comprehending the internal workings of a Kubernetes cluster. While master nodes manage the overall cluster and control plane components, worker nodes execute the workloads as containers. The collaboration between master and worker nodes is what allows Kubernetes to efficiently manage and orchestrate containerized applications at scale.
noob to master © copyleft
noob to master