Kubelet: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * Control Plane and Data Plane Concepts =Overview= =Cache=") |
|||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Each node runs an agent called kubelet, which is responsible with the node's registration with the cluster. Once a node is registered, its CPU, RAM and storage are pooled into the wider cluster pools of corresponding resources. The kubelet is watching the API server for work (pod) assignments and attempts to run them. If it is not successful for any reason, it reports the condition back to the API server. The task of actually running the pods is delegated to the local [[Kubernetes Control Plane and Data Plane Concepts#Container_Runtime|container runtime]]. | |||
=Cache= | =Cache= | ||
Revision as of 01:17, 24 August 2019
Internal
Overview
Each node runs an agent called kubelet, which is responsible with the node's registration with the cluster. Once a node is registered, its CPU, RAM and storage are pooled into the wider cluster pools of corresponding resources. The kubelet is watching the API server for work (pod) assignments and attempts to run them. If it is not successful for any reason, it reports the condition back to the API server. The task of actually running the pods is delegated to the local container runtime.