Difference between revisions of "Init:CrashLoopBackOff"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
[[kubectl get pods]] | [[kubectl get pods]] | ||
| − | elasticsearch-0 0/1 [[Init:CrashLoopBackOff]] 6 6m45s | + | elasticsearch-0 0/1 [[Init:]][[CrashLoopBackOff]] 6 6m45s |
elasticsearch-1 0/1 [[Init:]]CrashLoopBackOff 6 6m45s | elasticsearch-1 0/1 [[Init:]]CrashLoopBackOff 6 6m45s | ||
Revision as of 17:35, 18 July 2022
kubectl get pods
elasticsearch-0 0/1 Init:CrashLoopBackOff 6 6m45s elasticsearch-1 0/1 Init:CrashLoopBackOff 6 6m45s
Related
See also
kubectl get pods, kubectl describe pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff)- 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:
