Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
* <code>[[kubectl get events -A]]</code> | * <code>[[kubectl get events -A]]</code> | ||
* <code>[[kubectl describe pod]] your_pod</code> | * <code>[[kubectl describe pod]] your_pod</code> | ||
| − | * <code>[[kubectl describe nodes]]</code>, review [[conditions:]] | + | * <code>[[kubectl describe nodes]]</code>, review [[kubectl describe nodes (conditions:)|conditions:]] |
[[kubectl top]] or [[K9s]] | [[kubectl top]] or [[K9s]] | ||
Revision as of 06:44, 1 November 2022
kubectl logs your_podkubectl get events -Akubectl describe pod your_podkubectl describe nodes, review conditions:
kubectl top or K9s
Related
- Troubleshooting
- Kubernetes deployments
- Readiness probe errored
- Readiness, Liveness
- BackOff
- BackoffLimitExceeded
- Type
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
Unable to connect to the server
Insufficient cpu Insufficient memory
Diagram
See also
- 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:
