Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
* [[Reason]]: [[ProbeWarning]] | * [[Reason]]: [[ProbeWarning]] | ||
* [[Kubernetes Pod Disruptions]] | * [[Kubernetes Pod Disruptions]] | ||
| + | * [[NodeNotReady]] | ||
* <code>[[Unable to connect to the server]]</code> | * <code>[[Unable to connect to the server]]</code> | ||
[[Insufficient cpu]] | [[Insufficient cpu]] | ||
Revision as of 14:19, 22 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
- NodeNotReady
Unable to connect to the server
Insufficient cpu Insufficient memory MemoryPressure DiskPressure
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:
