Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
* [[Troubleshooting]] | * [[Troubleshooting]] | ||
* [[Kubernetes deployments]] | * [[Kubernetes deployments]] | ||
| + | * [[Kubernetes components]] | ||
* [[Readiness probe errored]] | * [[Readiness probe errored]] | ||
* [[Readiness]], [[Liveness]] | * [[Readiness]], [[Liveness]] | ||
Revision as of 16:09, 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
- Kubernetes components
- 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:
