Kubernetes NODEs
Kubernetes NODEs are likes Workers, they do real job, meaning they do what ever we specified in Master via are the manifest file i.e.YAML or JSON and Master then commands the NODE to get things done..
NODE has the following components:
- Kubelet
- Kube-proxy
- Container runtime (Which is Docker) , Docker is something, which can replace to rkt, whatever container runtime
Kubelet, It ias an agent, that runs on each NODE in the clusters.It make sure that containers are running in a POD.
They send the status message of healthy POD or damage POD to Master every time to ensure the containers are hale and hearty.
Basically this is the one, which is response for talking with the Kubernetes Master and ensure that POD which running inside the NODE healthy or damaged.
It doesn't try to resolve the issue, and why it is damaged, what is the resolution it has to take, No it won’t do any such things.
Container Runtime , It is a software, that is responsible for running containers.
Kubernetes supports several runtimes:
~Docker
~rkt
~runc etc..
Kube Proxy, it enables the Kubernetes service abstraction by maintaining network rules on the host & performing connections forwarding.
We can image , Kube Proxy as network manager or something, where it always know s that this is the network that the POD which is running in side the NODE that can be using.
It helps to create networking of PODs within NODEs.
PODs--> which is are the one which is responsible for running the container within it.A NODE can have one POD which is running inside it, or it can have multiple different POD running within it. So 1st part is called as Primary POD, and other POD are always called as backup PODs or secondary PODs.
These are the 3 simple components running within the NODE, and they do all the magic of clustering Kubernetes.
Thanks for reading 😊 ..….…...
