*Master Node *:
When a slave node needs some action to be performed it directly communicates with API server.
Now API server forwards the request of slave node to Controller Manager which then makes a check via API server to etcd Cluster of present scenario of requesting slave node.
Now after this, the Controller Manager checks if the present state is the same as the desired state or not.
If a match is not established, the Controller Manager instructs the Kube scheduler to do the needful.
*Slave Node *:
First of all a container is created with the help of a container engine inside a POD.
For creation of a POD kubelet makes a request to the API server and then the Master node plays its role.
After creation of POD, Kubeproxy assigns it IP address so that a POD can be uniquely identified.
Top comments (0)