Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
− | * Tools: <code>[[kubectl top]] | + | * Tools: <code>[[kubectl top]]<code>, <code>[[K9s]]</code> and <code>[[crictl]]</code></code> |
* {{FailedScheduling}} | * {{FailedScheduling}} |
Revision as of 13:31, 16 December 2022
kubectl logs your_pod
kubectl get events -A
kubectl describe pod your_pod
kubectl describe nodes
, reviewconditions:
- Tools:
kubectl top
,
K9s
andcrictl
Kubernetes components
Related
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: