Architecture

Kubernetes Architecture Overview

The architecture of Kubernetes is designed to provide a highly available and scalable platform for managing containerized applications. It consists of a master node and multiple worker nodes, each playing a crucial role in the orchestration process.

Master Node

The master node is responsible for managing the Kubernetes cluster. It contains the control plane components that make global decisions about the cluster (for example, scheduling) and detects and responds to cluster events (for example, starting up a new pod when a deployment's replicas field is unsatisfied).

Key Components of the Master Node

• API Server: The API server is the front end of the Kubernetes control plane. It exposes the Kubernetes API and is the entry point for all the REST commands used to control the cluster.
• Controller Manager: The controller manager is responsible for regulating the state of the system. It ensures that the desired state of the cluster matches the actual state.
• Scheduler: The scheduler watches for newly created pods with no assigned node and selects a node for them to run on.

Worker Nodes

Worker nodes are the machines that run the applications. Each worker node contains the necessary services to run pods, including the container runtime, kubelet, and kube-proxy.

Understanding the architecture of Kubernetes is essential for effectively deploying and managing applications in a cloud-native environment.