Difference between revisions of "Kubernetes node events"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
[[NodeHasNoDiskPressure]] | [[NodeHasNoDiskPressure]] | ||
[[NodeHasSufficientMemory]] | [[NodeHasSufficientMemory]] | ||
| − | [[ | + | [[NodeHasSufficientPID]] |
== Related == | == Related == | ||
Revision as of 10:14, 15 December 2022
kubectl get events -A | grep "node/"
Starting NodeReady RemovingNode
RegisteredNode InvalidDiskCapacity
NodeNotSchedulable RemovingNode NodeAllocatableEnforced NodeHasNoDiskPressure NodeHasSufficientMemory NodeHasSufficientPID
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:
