Error AtlasError Documentation and Resolution
Back to search

GKE

GKE node entered NotReady status

NotReady

A GKE node stopped reporting healthy readiness to the control plane, which can be caused by kubelet problems, runtime failures, resource pressure, or underlying node instability.

NotReadyruntime

Observed message

NotReady

Why it happens

  • The kubelet cannot report healthy node status to the control plane.
  • Node runtime, networking, or system components are unhealthy.
  • Resource pressure or deeper node instability is preventing the node from staying ready.

How to fix it

  1. Inspect node conditions and the Events section to see what changed before the node became NotReady.
  2. Review kubelet, container-runtime, and node-problem-detector logs for the underlying fault.
  3. Resolve the runtime, networking, or system issue that is preventing the node from reporting healthy status.

Official reference

Google Cloud: Troubleshoot nodes with the NotReady status in GKE

Related errors

0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.GKE could not schedule the pod because nodes did not have free requested pod ports401 UnauthorizedGKE image pull failed with 401 Unauthorizedi/o timeoutGKE image pull failed with i/o timeoutImagePullBackOffGKE pod failed to pull its container image

Explore more

runtimeBrowse more runtime errors
GKE NotReady: causes and fixes | Error Atlas