Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
* <code>[[kubectl top]] or [[K9s]]</code> | * <code>[[kubectl top]] or [[K9s]]</code> | ||
| + | |||
| + | * {{FailedScheduling}} | ||
== Related == | == Related == | ||
Revision as of 10:49, 16 December 2022
kubectl logs your_podkubectl get events -Akubectl describe pod your_podkubectl describe nodes, review conditions:
kubectl top or K9s
- FailedScheduling:
Insufficient cpu,Insufficient memory,timed out waiting for the condition,unbound immediate PersistentVolumeClaims
Related
- Kubernetes node events:
BackoffLimitExceeded, BackOff, NodeNotReady, FailedScheduling kubectl --cluster- Kubernetes components
- Readiness probe errored
- Readiness, Liveness
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
Unable to connect to the serverInsufficient cpuInsufficient memoryDiskPressurecrictlPLEG 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- Kubernetes node events: Kubernetes node events,
NodeNotSchedulable,NodeAllocatableEnforced,NodeHasNoDiskPressure, DiskPressure, NodeHasSufficientMemory,NodeHasSufficientPID,RegisteredNode,InvalidDiskCapacity,Starting,NodeReady,RemovingNode - 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:
