Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
* [[NodeNotReady]] | * [[NodeNotReady]] | ||
* <code>[[Unable to connect to the server]]</code> | * <code>[[Unable to connect to the server]]</code> | ||
| − | + | * <code>[[Insufficient cpu]]</code> | |
| − | + | * <code>[[Insufficient memory]]</code> | |
| − | + | * <code>[[MemoryPressure]]</code> | |
| − | + | * <code>[[DiskPressure]]</code> | |
* <code>[[crictl]]</code> | * <code>[[crictl]]</code> | ||
| − | + | * <code>[[PLEG is not healthy]]</code> | |
== See also == | == See also == | ||
Revision as of 11:34, 15 December 2022
kubectl logs your_podkubectl get events -Akubectl describe pod your_podkubectl describe nodes, review conditions:
kubectl top or K9s
Related
- Kubernetes node events
kubectl --cluster- Kubernetes deployments
- Kubernetes components
- Readiness probe errored
- Readiness, Liveness
- BackOff
- BackoffLimitExceeded
- Type
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
- NodeNotReady
Unable to connect to the serverInsufficient cpuInsufficient memoryMemoryPressureDiskPressurecrictlPLEG is not healthy
See also
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed- 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:
