Hey hello, Thanks for being here and this is my #2 blog with another step.

we may see many articles about this architecture but here its something different, i am going to put efforts in a way such that u can understand at ease.

caution::\

from this point read this blog till end or else avoid this without reading, i dont want my audience to leave the blog after exploring to certain extent its should be read completely so that u understand me better.

Excited :)

lets goo,

The kuberenetes arcitecture is divided into two parts :-

1. CONTROL PLANE

2. WORKER NODE

This is how it is, Now we will look into individual parts and their importance in it.

so we look into

CONTROL PLANE

first we will see the diagram of it and later we will be talking in detail,

by the way i need to introduce one more terminology for control plane and that is MASTER NODE

Now dont confuse yourself after looking into that picture, just you observe that it is a control plane and in it there are some other components, I am here dont worry i will explain you clearly about the things in the above picture, TRUST ME.

first u should believe that no matter what the applications/tools present in the above picture they are meant for some or other uses without their usage the developers should'nt have implemented them. so what i believe is we should study too deep into it, not at an glance we should learn about their usecases and importance.

so now we talk aboult the internal applications in control plane so starting by

API SERVER

This is like a gate in our home, assuming our home as a control plane if someone want to come in or going out this api server is imp, but to open the gate we need to put some external force for working of it so, here for communicating with this api server we use the tools called as KUBECTL and KUBE CONTROL

so we can call it as a gatekeeper to our entire cluster, dont confuse with the name cluster just assume that in a cluster both control plane and worker nodes wil be sitting in there by seeing each other.(we talk more about it when we should)

And main purpose of this api server is, it communicates with the worker node this api server just communicates only it doesnt have ability to fix the things only it is used for communication its just a medium. hope u got some clarity about api server

Now we look into other tool known as SCHEDULER

SCHEDULER

The name itself says it schedules, but what its going to schedule let me tell u, it schedules pods, Dont worry about pods we are going to learn them very elboratly, i cant explain this pods here, for explaining this pods i need to explain u about worker node, so later we will discuss about it,

so just remeber scheduler is like a sun, when sun rises the day in our home begins right, so it schedules pods ...

nxt we look into

CONTROL MANAGER

Think control manager as a teacher in a class, the teacher has the ability to control various types of students(their behaviour),

so in our cluster this control manager has the ability to control

• NODES -ENDPOINTS etc . depends on the cluster but it make sure that every node is running as per command or not if not it has the ability to control over ,

like teacher can handle students right, if a student is hyperactive, teacher has their own way to control the kid, depends on thier behaviour, if they are quiet good reflects teacher is idle ...

hope u got it:)

nxt is

ETCD

SO, what does etcd mean its like a storage almirahs in our house, where we store certain documets of our properties etc our house belongings which are more precious, i mean we store quiet imp things in it.

so in the same way we will call etcd as a database, and it has the backup data or any privacy data related to our cluster so thats it about etcd , actually this is the only 1st part we only talked about control plane and we should continue about worker nodes also, but not in this blog i will cotinue it in other blog...

Hope so u liked the content...:))

#happylearning

#fun