Kubelet
The kubelet is the Kubernetes node agent that manages Pod containers, ensures they run according to their specifications, and reports their status to the control plane.
Acing the Certified Kubernetes Administrator Exam, Second Edition
The kubelet binary is the executable program that runs the Kubernetes node agent.
- How it is used
- Supports node operations and troubleshooting by keeping Pod containers running and reporting their status to the control plane.
- How deep it goes
- Works through service checks, Pod events, node failure, static Pods, and DNS configuration; does not descend into kubelet implementation internals.
- Examples
- Uses a kind worker becoming NotReady after `systemctl stop kubelet` and a new Pod’s `/etc/resolv.conf` to verify DNS changes.
- What you can do after
- Diagnose/debug with it by checking its systemd status, correlating node and Pod symptoms, and inspecting failed control-plane containers.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains kubelet →
Kubernetes in Action, Second Edition
The kubelet is the agent on a Kubernetes node that manages the applications assigned to that node and reports their status.
- How it is used
- Runs assigned application instances on worker nodes and reports their status through the API.
- How deep it goes
- Traces startup, node registration, deletion, and loss of API contact, but defers detailed container shutdown behavior.
- Examples
- Uses pod events to show image pulls and container starts, and a disconnected node to show delayed termination.
- What you can do after
- Diagnose/debug with `kubectl describe pod` events and node status to distinguish startup steps from loss of node contact.
Read how Kubernetes in Action, Second Edition explains kubelet →
Kubernetes for Developers
The kubelet is a Kubernetes node agent that communicates with the control plane and manages container lifecycle on its node.
- How it is used
- Manages container lifecycles on nodes while communicating with the Kubernetes control plane.
- How deep it goes
- Distinguishes local restarts from scheduler-driven Pod reallocation but does not detail kubelet internals.
- Examples
- Uses crashed-container restarts, liveness and readiness failures, and node failures that trigger Pod reallocation.
- What you can do after
- Understand which failures the kubelet handles locally and which failures the scheduler handles by reallocating Pods.
Related concepts
- kubernetes api serveruses · The Kubernetes API server is the control-plane component that exposes, validates, and processes the Kubernetes API for managing cluster resources and state.
- poduses · A Kubernetes Pod is the smallest deployable unit in Kubernetes, grouping one or more co-located containers that share networking and other resources.
- Container Runtime Interfaceuses · The Container Runtime Interface is a Kubernetes standard interface through which kubelets communicate with and manage container runtimes.
- Kubernetes worker nodepart of · A Kubernetes worker node is a physical or virtual machine in a cluster that provides compute resources and runs scheduled Pods and node-level services.
- workerequivalent to · A worker is a person or computational execution unit assigned to perform a task as part of a larger system or activity.
- background processingkind of · Background processing is the execution of work independently of the immediate interactive or request-handling flow, so foreground activity need not wait for its completion.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.