This page includes the reference list for the node event reasons that Kubernetes® uses in Version v1.21.3.

Warning Event Type

Event ReasonMessage
KubeletSetupFailedError configuring root directory: %v || error creating podresources directory: %v || error creating podresources directory: %v || failed to create directory %q: %v", ContainerLogsDir, err || "failed to start OOM watcher %v", err
EvictionThresholdMetAttempting to reclaim %{resourceToReclaim}.
InvalidDiskCapacity

Invalid capacity 0 on image filesystem.

FreeDiskSpaceFailed

Failed to garbage collect required amount of images. Wanted to free %d bytes, but freed %d bytes", amountToFree, freed.

RebootedNode %{node name} has been rebooted, boot id: {bootId}
readOnlySysFSCRI error: /sys is read-only: cannot modify conntrack limits, problems may arise later (If running Docker, see docker issue #24000).
ContainerGCFailed[ Failed to List Container, Failed to List pod Sandboxes, failed to read podLogsRootDirectory]
ImageGCFailed

MissingClusterDNS

Kubelet does not have ClusterDNS IP configured and cannot create Pod using %{ClusterFirst} policy. Falling back to %{Default} policy.

FailedToCreateRoute

"Could not create route %{node.uid} %{CIDR Ip range to which this rule applies } for node %{node name} after %{time.since(starttime)}: %{err}"

FailedToStartProxierHealthcheck

"Failed to start proxier healthz on %s: %v", proxyhealthserver.bindAddress, err

CheckLimitsForResolvConf

Check limits for resolv.conf failed at file open.

CheckLimitsForResolvConf

Check limits for resolv.conf failed at parse resolv.conf: %{err} ||

Resolv.conf file %{Path/to/resolverconfig/file} contains search line consisting of more than 6 domains! ||

Resolv.conf file %{Path/to/resolverconfig/file} contains a search path which length is more than allowed 253 chars! ||

Resolv.conf file %{Path/to/resolverconfig/file} contains search line which length is more than allowed 256 chars!

OwnerRefInvalidNamespace

ownerRef %{invalid identity} does not exist in namespace %{namespace}.

VolumeAttachmentStuck

Volume stuck in attaching state - node needs reboot to fix impaired state.

FailedNodeAllocatableEnforcement

Failed to update Node Allocatable Limits %q: %v", cgroupRoot, err

HostNetworkNotSupportedHost Network not Supported
NilShaperUndefined Shaper

Normal Event Type

Event ReasonMessage

NodeHasInsufficientMemory

Node %{name} status is now: %{event}

NodeHasSufficientMemory

Node %{name} status is now: %{event}

NodeHasDiskPressure

Node %s status is now: %s

NodeHasNoDiskPressure

Node %s status is now: %s

NodeHasInsufficientPID

Node %s status is now: %s

NodeHasSufficientPID

Node %s status is now: %s

NodeNotSchedulable

Node %s status is now: %s

NodeSchedulable

Node %s status is now: %s

NodeReady

Node %s status is now: %s

NodeNotReady

Node %s status is now: %s

NodeControllerEviction

"Marking for deletion Pod %s from Node %s", pod.Name, nodeName

NodeAllocatableEnforced

"Updated Node Allocatable limit across pods" ||

"Updated limits on system reserved cgroup %v", nc.SystemReservedCgroupName ||

"Updated limits on kube reserved cgroup %v", nc.KubeReservedCgroupName

RegisteredNode

Registered Node %v in Controller

RemovingNode

Removing Node %v from Controller

DeletingAllPods

Deleting all Pods from Node %v

Synced

Node synced successfully

DeletingNode

Deleting node %{node-name} because it does not exist in the cloud provider.

CloudCIDRAllocatorInvalidPodCIDR

"Node %q has an invalid PodCIDR: %q", op.node.Name, op.node.Spec.PodCIDR

CloudCIDRAllocatorInvalidMode

"controller cannot allocate CIDRS in mode %q", sync.mode

CloudCIDRAllocatorMismatch

"Node.Spec.PodCIDR != cloud alias (%v != %v)", node.Spec.PodCIDR, aliasRange(ip and mask)



OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.