Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
== Related == | == Related == | ||
− | * [[Kubernetes node events]]: <code>[[BackoffLimitExceeded]]</code> | + | * [[Kubernetes node events]]: <code>[[BackoffLimitExceeded]], [[BackOff]]</code> |
* <code>[[kubectl --cluster]]</code> | * <code>[[kubectl --cluster]]</code> | ||
* [[Kubernetes components]] | * [[Kubernetes components]] | ||
* [[Readiness probe errored]] | * [[Readiness probe errored]] | ||
* [[Readiness]], [[Liveness]] | * [[Readiness]], [[Liveness]] | ||
− | |||
− | |||
* [[Type]] | * [[Type]] | ||
* [[Reason]]: [[ProbeWarning]] | * [[Reason]]: [[ProbeWarning]] |
Revision as of 10:43, 16 December 2022
kubectl logs your_pod
kubectl get events -A
kubectl describe pod your_pod
kubectl describe nodes
, review conditions:
kubectl top or K9s
Related
- Kubernetes node events:
BackoffLimitExceeded, BackOff
kubectl --cluster
- Kubernetes components
- Readiness probe errored
- Readiness, Liveness
- Type
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
- NodeNotReady
Unable to connect to the server
Insufficient cpu
Insufficient memory
MemoryPressure
DiskPressure
crictl
PLEG 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: