Difference between revisions of "CrashLoopBackOff"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
* <code>[[ebs-csi-controller]]</code> | * <code>[[ebs-csi-controller]]</code> | ||
* <code>[[kubectl get pods]]</code> | * <code>[[kubectl get pods]]</code> | ||
+ | * <code>[[pod_workers.go]]</code> | ||
== See also == | == See also == |
Revision as of 12:04, 7 December 2023
CrashLoopBackOff
Init:CrashLoopBackOff
Related
- OOM
kubectl get pods -A | grep CrashLoopBackOff
kubectl describe pods
ebs-csi-controller
kubectl get pods
pod_workers.go
See also
- Kubernetes init containers:
kubectl get pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff), initContainers:
- 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
- Pods:
kubectl apply
,kubectl [ pod get | top | delete | describe pods ]
,InitContainers, PodInitializing, CrashLoopBackOff, ImagePullPolicy:, NodeAffinity, NodeSelector, Terminated
Advertising: