Member-only story
To begin with let us first understand what and why of “kubernetes”. Kubernetes is an open- source system for automating deployment, scaling and managing the containerized applications [ Containerized applications are those applications that run in isolated runtime environments called containers. Containers encapsulate an application with all its dependencies, including system libraries, binaries, and configuration files ]. Answering the why : Containers appeal to organizations for a broad range of workloads. But provisioning and operationalizing containers at scale, often in concert with microservices, is not for weekend enthusiasts. Especially for stateful apps (such as databases), it requires planning, and most experts say an orchestration tool is a must. That’s where Kubernetes comes in. Kubernetes eases the burden of configuring, deploying, managing, and monitoring even the largest-scale containerised applications.
[ also referred as K8s ~ as it has 8 alphabets between k and s]
In this article we will get a clarity on the Kubernetes architecture ; the control plane components and the worker node components; along with features like api-server, scheduler, etcd, and control manager. Under worker nodes, we shall cover kubectl, kubelet, and kube-proxy.
Moving on further; So what is a Kubernetes control plane? The control plane is a global decision-maker for the cluster, meaning it controls scheduling. It is also responsible for maintaining overall cluster behaviour. It is the central management point for the cluster, and it consists of a number of different components that work together to manage the cluster and ensure that the desired state of the system is maintained.
The control plane has following components:
API server (kube-apiserver)
The API server is the gateway to the Kubernetes cluster. It is the central touch point that is accessed by all users, automation, and components in the Kubernetes cluster. API server inside the master node is where all the administrative tasks will be performed. REST commands then go to the API server that will process and validate the requests. Upon request, the cluster’s resulting state will be stored based on the distributed key value. i.e. Operating the Kubernetes API server involves three core…
