Kubernetes Architecture

Understand k8s architecture the easy way!!!

ยท

2 min read

Kubernetes Architecture

Understanding K8s can be really challenging ๐Ÿ˜Ÿ ๐Ÿ˜Ÿ

So here I am ๐Ÿ™‚ with the 1 liner simple explainations of the different components of K8s ๐ŸŽ‰ image.png

Let us talk first about the API server. image.png Api server acts as frontend service . Users ,Management devices , Cli's all talk to the API Server to interact with the k8s clster.

image.png

etcd - etcd is a strongly consistent, distributed key-value store that provides a reliable way to store data that needs to be accessed by a distributed system.

Used to store all the data managed by the cluster in the form of key-value pairs. eg: multiple masters and nodes storage.

Scheduler- Distributes work across different containers .

Controller- Brain behind orchaestration. When nodes / containers / end points get down they respond by bringing new containers and replacing them.

Container runtime -> Underlying software used to run the containers. Eg:- Docker, Rocket, CRI-O.

Kubelet - Agent that runs on each node in the cluster. Responsible that containers are running on each node as expected.

You might be thinking what is the difference between master and slave nodes. By far both are nodes but they have different services based on the below diagram.

image.png

That is all in this blog โœจ , I will keep bringing more blogs and simplifying your devops journey ๐ŸŽˆ

Subscribe so that you dont miss โœจ Thank you.

ย