CRE-2025-0048

Kubelet node not ready due to a DNS hostname resolution failureLow

Impact: 5/10

Mitigation: 3/10

CRE-2025-0048View on GitHub

KubeletKubernetesDNSPublic

Description

A Kubernetes worker node has entered the NotReady state.

Cause

• The node's DNS hostname resolution failed.

Mitigation

• Check the node's FQDN in /etc/hosts and ensure it is resolvable from the control-plane.

References

• https://github.com/kelseyhightower/kubernetes-the-hard-way/issues/822