Difference between revisions of "Back-off restarting failed container (BackOff)"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
== See also == | == See also == | ||
| + | * {{kubectl events}} | ||
* {{K8s troubleshooting}} | * {{K8s troubleshooting}} | ||
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Revision as of 15:22, 6 September 2022
kubectl get events -A Warning BackOff 1s (x9 over 95s) kubelet Back-off restarting failed container
kubectl describe pod your-pod Warning BackOff 3m20s (x34 over 8m21s) kubelet Back-off restarting failed container
See also
- 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:
