Kubernetes and its architecture with component
Let’s start with very basic
What is Kubernetes?
Kubernetes is an open-source container orchestration tool. It simplifies the management of containerized applications by automating tasks such as scaling, deployment, and load balancing.
Why choose Kubernetes over Docker alone?
While Docker is excellent for containerization, it has limitations in dynamic traffic management. For example, if the traffic on your website suddenly spikes, Docker containers cannot automatically scale themselves to handle the increased load.
This is where Kubernetes comes in. Kubernetes automatically manages tasks like scaling pods or nodes to ensure your application remains responsive, even during traffic fluctuations.
Kubernetes components
Kubernetes works on master slave architecture
There are primarily 7 components in k8
Kubernetes operates on a control plane and worker node architecture. The primary components are:
Etcd: A distributed key-value database that serves as the central data store for cluster state and configuration.
API Server: The entry point of the cluster and the front end of the control plane, exposing the Kubernetes API for management. It allows the client to communicate to the cluster using commands like kubectl.
Scheduler: Assigns Pods to nodes based on resource requirements, policies, and availability.
Controller Manager: Runs various controllers, such as the Node Controller (manages node health), Job Controller (manages job resources), and Service Account Controller (manages service accounts). It also ensures that the desired state of the Kubernetes cluster is maintained.
Kubelet: The primary agent running on each worker node, ensuring that containers in Pods are healthy and running as specified.
Kube-Proxy: Handles Pod networking, including routing, network rules, and load balancing.
Container Runtime: Manages the lifecycle of containers on worker nodes. Examples include Docker.
Thanks, Cheers!
