Components in Kubernetes Architecture
- Master Node: The master node is the central control plane of a Kubernetes cluster. It is responsible for managing the cluster and the various nodes in it. The master node consists of several components, including the API server, etcd, scheduler, and controller manager.
- Worker Node: Worker nodes are the machines (virtual or physical) where your applications are deployed and run. These nodes run the required services to execute the containers, such as container runtime and kubelet.
- Pod: A pod is the smallest deployable unit in Kubernetes. It is a logical host for one or more containers. All containers in a pod run on the same node and share the same network namespace.
- Service: A service is an abstraction that defines a logical set of pods and a policy by which to access them. A service can be exposed as a load balancer or a DNS entry.
- Volume: A volume is a persistent storage for your application data. It allows your application to retain data even if the pod or the node fails.
- Namespace: A namespace is a virtual cluster inside a physical cluster. It is used to divide resources and limit access to resources within a cluster.
How To Set Up Master-Slave Architecture Locally in Kubernetes?
Pre-requisite: Kubernetes
Kubernetes is an open-source container orchestration system for automating containerized applications’ deployment, scaling, and management. It was originally designed by Google and is now maintained by the Cloud Native Computing Foundation (CNCF). Kubernetes helps you deploy and manage containerized applications at scale more efficiently and resiliently. It provides features such as declarative configuration, self-healing, and horizontal scaling.