Kubernetes terms made easy

when we have docker compose and we can define rules to run our containerized applications over there ... so why do we need k8s...?

Well we can certainly manage very small containers... but handling large scale applications through this will certainly be a nightmare...

Because ... large apps will need to scale automatically.. and docker compose requires manual intervention and scripting .. ahhh who will re invent the wheel...

Let's k8s do this...

Now when we know the importance of k8s .. we have to learn it's core components and it's architecture level working...

k8$ environment have a company named ... control pane .. who is responsible for managing and running kubernetes clusters .... 

This company, named control pane.. have a CEO.. named, API Server ...I wasn't talking about the actual CEO of kubernetes 😅... just an analogy...

Every one discuss there matters with API server ... and api server talks to everyone ... It's kind of a brain of the company... 

Next comes the executive assistant of the CEO... named Scheduler... who is responsible to arrange meetings of different teams.. with API server... in short... scheduler determines which worker node in the cluster is available or sitting free.. so scheduler can assign some task to that worker node .. tasks could be like run this application on this pod ... and do this bla bla bla...🙄

One more guy is there... let's call him .. hmmm .. 🤔... Chief Operating Officer.... that's sounds like good name .. but I'm not in the management so I don't know much about hierarchy...

That COO is named as Controller manager... responsible for managing replica sets, deployment jobs .. etc etc etc...

now we have a cluster .. which is the set of worker nodes ..

Worker nodes , the actual working employees I guess... contains..

kubectl...

container run

kube-proxy

pods

containers

kubectl is the manager over here responsible for communicating with the CEO... talking tasks with him ... and assigning to the teams ..

other then that all are employees...

container run will take the commands from kubectl and do necessary like pulling any image from the repository .. etc...

kube-proxy is responsible for managing the route tables... like which pod is going to communicate with which one...etc...

pods and containers you guys knows...