Difference between revisions of "Kubernetes node events"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
[[NodeAllocatableEnforced]] | [[NodeAllocatableEnforced]] | ||
[[NodeHasNoDiskPressure]] | [[NodeHasNoDiskPressure]] | ||
| + | [[NodeHasSuficientMemory]] | ||
== Related == | == Related == | ||
Revision as of 10:13, 15 December 2022
kubectl get events -A | grep "node/"
Starting NodeReady RemovingNode
RegisteredNode InvalidDiskCapacity
NodeNotSchedulable RemovingNode NodeAllocatableEnforced NodeHasNoDiskPressure NodeHasSuficientMemory
Related
See also
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed- Kubernetes nodes,
node.kubernetes.ioK8s Node controller (node-controller),MemoryPressure, DiskPressure, NodeHasDiskPressure, events, NodeNotReady, Node-pressure Eviction, RemovingNode, ProviderID,kubectl node-shell, kubectl describe nodes
Advertising:
