Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
| − | * <code>[[kubectl top]] or [[K9s]]</code> | + | * Tools: <code>[[kubectl top]] or [[K9s]], [[crictl]]</code> |
* {{FailedScheduling}} | * {{FailedScheduling}} | ||
| Line 19: | Line 19: | ||
[[Kubelet]] | [[Kubelet]] | ||
* <code>[[PLEG is not healthy]]</code> | * <code>[[PLEG is not healthy]]</code> | ||
| − | |||
| − | |||
== Related == | == Related == | ||
Revision as of 11:07, 16 December 2022
kubectl logs your_podkubectl get events -Akubectl describe pod your_podkubectl describe nodes, review conditions:
- Tools:
kubectl top or K9s, crictl
- FailedScheduling:
Insufficient cpu,Insufficient memory,timed out waiting for the condition,unbound immediate PersistentVolumeClaims
Kubernetes components
Related
- Kubernetes node events:
BackoffLimitExceeded, BackOff, NodeNotReady, FailedScheduling kubectl --clusterReadiness probe errored- Readiness, Liveness
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
Unable to connect to the server, ~/.kube/configDiskPressureCalculateExpectedPodCountFailed
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:
