DEV Community

Cover image for Architecture of Kubernetes on a high level
Pradipta
Pradipta

Posted on

Architecture of Kubernetes on a high level

As discussed in the previous post of the series, Kubernetes has one Master node and multiple Worker nodes. Master node monitors all Worker nodes. In Kubernetes, there must be at least one Cluster, one Master node and one Worker node.

Master Node : It has four components. They are API Manager, Scheduler, Controller Manager and ETCD.

API Server acts as a Cluster Gateway. It can be used using command line tool kubectl or through Kubernetes Dashboard.

Scheduler schedules PODs in the Worker nodes based of availability of CPU and Memory. Scheduler gets the information of Worker nodes from ETCD.

Whenever a POD or Node gets crashed, ReplicaSet creates a new one. Controller Manager manages the process of Scheduling the same as per availability working with the Scheduler.

Worker Node : It has three components. They are kubelet, kube-proxy and Container runtime.

Kubelet is an agent that runs on each Worker node and communicates with Master node using API Server.

Kube-Proxy is a network agent that runs on each Worker node.

Container runtime helps to run container inside PODs.

Top comments (0)