Node NotReady from Memory/CPU Saturation
Resource Contention
AKS nodes enter NotReady state when memory or CPU saturation causes kubelet and containerd to become unresponsive. This occurs when resource limits are exceeded or PSI metrics indicate sustained pressure.
Azure AKS insight details requires a free account. Sign in with Google or GitHub to access the full knowledge base.
Sign in to access