Difference between revisions of "Job has reached the specified backoff limit"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Job has reached the specified [[backoff]] limit | + | |
| + | [[kubectl get events]] | ||
| + | your_namespace 30m Warning [[BackoffLimitExceeded]] [[job/]]your-job27740460 Job has reached the specified [[backoff]] limit | ||
| + | |||
== Related == | == Related == | ||
* <code>[[BackOff]]</code> | * <code>[[BackOff]]</code> | ||
| + | [[kubectl get jobs]] | ||
== See also == | == See also == | ||
Latest revision as of 05:49, 29 September 2022
kubectl get events your_namespace 30m Warning BackoffLimitExceeded job/your-job27740460 Job has reached the specified backoff limit
Related[edit]
kubectl get jobs
See also[edit]
- 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:
