Difference between revisions of "Kubernetes events"
Jump to navigation
Jump to search
| (14 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Normal]] | [[Warning]] | ||
| + | |||
| + | * [[Kubernetes node events]]: <code>[[kubectl get events -A ]]| grep "node/"</code> | ||
| + | * [[jobs/]] | ||
| + | * [[service/]] | ||
| + | |||
| + | <code>[[events.k8s.io]]</code> | ||
| + | |||
| + | * {{FailedScheduling}} | ||
| + | * {{kubectl get events}} | ||
| + | |||
| + | == [[Node events]] == | ||
| + | * {{Kubernetes nodes events}} | ||
| + | |||
| + | == Examples == | ||
| + | {{nginx-ingress events}} | ||
| − | |||
| − | |||
| − | |||
== Related == | == Related == | ||
* [[Kubernetes controller manager]] | * [[Kubernetes controller manager]] | ||
* [[Kubernetes node-problem-detector]] | * [[Kubernetes node-problem-detector]] | ||
| + | * [[Kubernetes ports]] | ||
| + | * [[Pulling image]] | ||
| + | * [[ECS events]] | ||
| + | * [[kubectl events]] | ||
| + | * [[Rancher]]: core -> [[Events]] | ||
== See also == | == See also == | ||
| + | * {{kubectl events}} | ||
* {{K8s troubleshooting}} | * {{K8s troubleshooting}} | ||
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Latest revision as of 16:08, 23 January 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
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:
