Difference between revisions of "Kubernetes events"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 34: | Line 34: | ||
* <code>[[FailedBuildModel]]</code> | * <code>[[FailedBuildModel]]</code> | ||
* [[Startup probe failed]] | * [[Startup probe failed]] | ||
| + | * <code>[[Successfully pulled image]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 13:06, 2 October 2024
Normal | Warning
- Kubernetes node events:
kubectl get events -A | grep "node/" - jobs/
- service/
- 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
Contents
Node events[edit]
- Kubernetes node events: Kubernetes node events,
NodeNotSchedulable,NodeAllocatableEnforced,NodeHasNoDiskPressure, DiskPressure, NodeHasSufficientMemory,NodeHasSufficientPID,RegisteredNode,InvalidDiskCapacity,Starting,NodeReady,RemovingNode
Examples[edit]
ingress-nginx 53m Normal UpdatedLoadBalancer service/nginx-ingress-controller Updated load balancer with new hosts ingress-nginx 54m Warning UnAvailableLoadBalancer service/nginx-ingress-controller There are no available nodes for LoadBalancer
Related[edit]
- Kubernetes controller manager
- Kubernetes node-problem-detector
- Kubernetes ports
- Pulling image
- ECS events
- kubectl events
- Rancher: core -> Events
FailedBuildModel- Startup probe failed
Successfully pulled image
See also[edit]
- Kubernetes events, Kubernetes node events:
[ Normal | Warning ],kubectl events, kubectl get events:BackOff,FailedMount, FailedAttachVolume, TaintManagerEviction, InvalidDiskCapacity,FailedScheduling, kubectl describe events, Unhealthy,conditions:, UpdatedLoadBalancer, BackoffLimitExceeded - 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:
