Well usually everyone goes with explaining containers and pod, like workloads but we feel it’s better to know architectures first with those questions in the head. we will explain about work loads but now lets jump in with architecture and components.
Kubernetes Architecture
What is Kubernetes cluster ?
A Kubernetes cluster is a group of physical or virtual machines, known as nodes, that work together to provide a scalable, fault-tolerant, and high-performance computing environment for deploying containerized applications.
Key Components of a Kubernetes Cluster:
1. Master Node: The control plane component responsible for managing the cluster, including scheduling pods (containerized applications), managing networking, and providing storage.
2. Worker Nodes: The nodes that run the containers and provide computing resources to the cluster.
Characteristics of a Kubernetes Cluster:
1. Horizontal Scaling: Allows you to add or remove worker nodes as needed to match changes in workload demand.
2. Self-healing: Automatically detects and recovers from node failures, ensuring high availability for your applications.
3. Resource Management: Enables efficient resource utilization and allocation across the cluster.
4. Network Policy Enforcement: Provides fine-grained control over network traffic between pods.
Types of Kubernetes Clusters:
1. Single-Node Cluster (Minikube): A development environment that runs on a single machine.
2. Multi-Node Cluster (Kubeadm, Kubespray): A production-ready cluster with multiple nodes, managed by tools like Kubeadm or Kubespray.
In summary, a Kubernetes cluster is a distributed system consisting of one or more nodes that work together to provide a scalable, fault-tolerant, and high-performance what is Kubernetes clusterA Kubernetes cluster is a group of physical or virtual machines, known as nodes, that work together to provide a scalable, fault-tolerant, and high-performance computing environment for deploying containerised applications.
What is master node ?
In a Kubernetes cluster, the Master Node (also known as the Control Plane) is a special node responsible for managing the entire cluster. It’s the brain of the operation, making decisions on how to schedule pods (containerized applications), manage networking, and provide storage.
Key Responsibilities of a Master Node:
1. Scheduling: The master node schedules pods onto worker nodes based on resource availability, priorities, and other factors.
2. API Server: Provides a RESTful API for clients (like `kubectl`) to interact with the cluster, including creating, updating, and deleting resources like pods, services, and deployments.
3. Controller Manager: Runs various controllers that manage the cluster’s state, such as pod creation, deletion, and scaling.
4. Scheduler: Responsible for scheduling pods onto worker nodes based on resource availability and other factors.
Components of a Master Node:
1. etcd: A distributed key-value store that maintains the cluster’s configuration and state.
2. API Server: The RESTful API server that handles client interactions with the cluster.
3. Controller Manager: Runs various controllers that manage the cluster’s state.
4. Scheduler: Responsible for scheduling pods onto worker nodes.
Why is a Master Node important?
1. Cluster Management: The master node manages the entire cluster, making decisions on resource allocation and pod placement.
2. API Server: Provides a central point of interaction with the cluster through the `kubectl` command-line tool.
3. Controller Manager: Runs various controllers that ensure the cluster’s state is accurate and consistent.
What is worker node?
In a Kubernetes cluster, a Worker Node is a machine that runs containers and provides computing resources to the cluster. Worker nodes are responsible for executing tasks (called “pods”) scheduled by the master node.
Key Characteristics of a Worker Node:
1. Container Execution: Runs containers on behalf of the master node, providing the necessary resources (CPU, memory, storage) for each pod.
2. Resource Provisioning: Provides computing resources (e.g., CPU, memory) to pods scheduled by the master node.
3. Pod Management: Manages pod lifecycle events such as creation, deletion, and scaling.
4. Networking: Provides network connectivity between pods and with external networks.
Types of Worker Nodes:
1. Regular Node: A standard worker node that runs containers on behalf of the master node.
2. Master Node: In some cases, a single machine can act as both the master node (Control Plane) and a worker node (Compute Node).
Key Responsibilities of a Worker Node:
1. Run Containers: Execute containers based on pod specifications provided by the master node.
2. Provide Resources: Allocate computing resources to pods as needed.
3. Monitor Pods: Monitor pod health, restart failed pods, and handle other lifecycle events.
Why are Worker Nodes important?
1. Compute Power: Provide the necessary compute power for running containers.
2. Resource Allocation: Manage resource allocation across pods.
3. Pod Execution: Execute tasks (pods) on behalf of the master node.
