Difference between revisions of "CrashLoopBackOff"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 1: | Line 1: | ||
* <code>CrashLoopBackOff</code> | * <code>CrashLoopBackOff</code> | ||
* <code>[[Init:CrashLoopBackOff]]</code> | * <code>[[Init:CrashLoopBackOff]]</code> | ||
| + | |||
| + | * <code>[[kubectl get pods -A]] | grep CrashLoopBackOff</code> | ||
| Line 7: | Line 9: | ||
== Related == | == Related == | ||
* [[OOM]] | * [[OOM]] | ||
| − | |||
* <code>[[kubectl describe pods]]</code> | * <code>[[kubectl describe pods]]</code> | ||
* <code>[[ebs-csi-controller]]</code> | * <code>[[ebs-csi-controller]]</code> | ||
Revision as of 10:51, 15 April 2025
CrashLoopBackOffInit:CrashLoopBackOff
kubectl get pods -A | grep CrashLoopBackOff
back-off 20s restarting failed container
Related
- OOM
kubectl describe podsebs-csi-controllerkubectl get podspod_workers.go- K8s probes
- Kubernetes restartPolicy
See also
- Kubernetes init containers:
kubectl get pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff), initContainers:,Init:0/1 - CrashLoopBackOff
- 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,CrashLoopBackOff - Pods:
kubectl apply,kubectl [ pod get | top | delete | describe pods ],InitContainers, PodInitializing, CrashLoopBackOff, ImagePullPolicy:, NodeAffinity, NodeSelector, Terminated
Advertising:
