Difference between revisions of "Kubernetes events"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
[[events.k8s.io]] | [[events.k8s.io]] | ||
+ | |||
+ | * {{FailedScheduling}} | ||
+ | * {{kubectl get events}} | ||
+ | * {{Kubernetes nodes events}} | ||
Revision as of 13:35, 16 December 2022
events.k8s.io
- FailedScheduling:
Insufficient cpu
,Insufficient memory
,timed out waiting for the condition
,unbound immediate PersistentVolumeClaims
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
Related
See also
- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod
, Liveness, Readiness,Kubernetes events
, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling
,errImagePull, ImagePullBackOff
, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising: