Difference between revisions of "Kubernetes node events"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
* <code>[[Starting]] [[Starting kubelet]]</code> | * <code>[[Starting]] [[Starting kubelet]]</code> | ||
| + | |||
* <code>[[NodeReady]]</code> | * <code>[[NodeReady]]</code> | ||
* <code>[[RemovingNode]]</code> | * <code>[[RemovingNode]]</code> | ||
| + | * <code>[[RegisteredNode]]</code> | ||
| + | |||
| − | |||
* <code>[[InvalidDiskCapacity]]</code> | * <code>[[InvalidDiskCapacity]]</code> | ||
Revision as of 11:16, 30 December 2022
kubectl get events -A | grep "node/"
NodeNotSchedulableNodeAllocatableEnforcedNodeHasNoDiskPressureDiskPressureNodeHasSufficientMemoryNodeHasSufficientPID
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 node events: Kubernetes node events,
NodeNotSchedulable,NodeAllocatableEnforced,NodeHasNoDiskPressure, DiskPressure, NodeHasSufficientMemory,NodeHasSufficientPID,RegisteredNode,InvalidDiskCapacity,Starting,NodeReady,RemovingNode - 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:
