kubelet.exe

Kubernetes Kubelet Node Agent

CPU Usage

N/A

Memory

N/A

Location

N/A

Publisher

N/A

Notes

Respect drainage procedures before actions on a node; after restart, verify node re-registers with the API server and pods resume healthy operation.

Impacts

Killing kubelet can disrupt pod management on the node, causing pods to terminate or become unhealthy until kubelet restarts.

Is Safe To Kill

Recommended Actions

If kubelet is unresponsive, attempt graceful restart of the service, inspect container runtime and node health, then verify cluster state after restart.

What is kubelet.exe?

kubelet.exe is the Windows binary that runs the Kubernetes node agent on a Windows worker. It registers the node with the API server, watches pod specifications, starts and stops containers via the configured runtime, enforces resource limits, and reports health and metrics back to the control plane. Understanding its role helps diagnose node-level issues.

Kubelet.exe coordinates with the container runtime (containerd or dockerd) to ensure pods run as defined, handles readiness and liveness checks, mounts volumes, and reconciles desired vs. actual state. It runs as a Windows service and continuously reports status to the Kubernetes API server.

Is it Safe?

Is it a Virus?

: Confirm kubelet.exe exists at the standard Windows install location.
: Verify the binary signature is from the official Kubernetes release signer.
: Compute and compare the SHA256 hash against the published release hash.
: Run a full antivirus and malware scan on kubelet binaries and config folders.

Why is it Running?

Reasons it's running:

Kubelet is starting up and registering the node: On boot or when a node joins the cluster, kubelet initializes, registers with the API server, and begins managing pod lifecycles on that node.
Kubelet is reconciling pod state with the API server: Kubelet periodically reconciles the desired pod specs with the actual containers, ensuring containers run as defined and resources are allocated.
Container runtime activity drives workload execution: Kubelet delegates to containerd or dockerd; heavy image pulls, sandbox creation, or pod startup can elevate resource usage temporarily.
Rolling updates and autoscaling actions: During upgrades or autoscaler adjustments, kubelet creates or terminates pods, increasing activity and log throughput temporarily.
Misconfigurations or flag changes require restart: Incorrect kubelet configuration or changed flags may cause restarts or unusual behavior until the config is corrected.

Can I Disable or Remove It?

Common Problems

Common Causes & Solutions

Misconfigured service, missing certificates, or incorrect path to runtime.: Reinstall kubelet, verify service configuration, and ensure certificates and runtime binaries exist at expected locations.
Large number of pods, frequent image pulls, or verbose logging.: Review running pods, throttle logging level, adjust resource limits, and consider splitting workloads or upgrading node resources.
Node not Ready or runtime cannot pull images.: Check kubelet and container runtime status, confirm network access, and ensure imagePullSecrets and private registries are configured correctly.
Missing credentials or invalid secrets.: Create or update imagePullSecrets with valid credentials and attach them to the namespace or service account used by the pods.
Config drift or invalid flags.: Validate kubelet-config.yaml, review recent changes, and revert to a known-good configuration; restart the kubelet service.
Incompatible binaries or runtime mismatch.: Verify Kubernetes version compatibility, reapply the upgrade in a controlled rollout, and ensure container runtime is compatible.

Frequently Asked Questions

Is kubelet.exe safe to run on Windows?

Yes, when obtained from official Kubernetes releases and verified with signatures. Always validate the install path and digital signature.

Why is kubelet.exe using high CPU on my Windows node?

Potential workload spikes, image pulls, or frequent pod restarts can drive CPU usage; check pod metrics, logs, and container runtimes for root causes.

Can I disable kubelet on a Windows node?

Disabling kubelet stops pod management on that node. Only do during maintenance after cordon/drain and ensure workloads are redistributed.

How do I update kubelet on Windows?

Update via your Kubernetes release channel; replace the kubelet.exe binary, update config if needed, and restart the kubelet service.

Where can I find kubelet logs on Windows?

Kubelet logs typically appear in the Kubernetes log directory (for example: C:\ProgramData\Kubernetes\logs\kubelet.log) or via Windows Event Viewer depending on setup.

What config controls kubelet behavior on Windows?

Kubelet behavior is controlled by kubelet-config.yaml and startup flags passed by the cluster, including resource limits, runtime settings, and node labels.