Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
Line 54: | Line 54: | ||
* <code>[[kubectl exec]]</code> | * <code>[[kubectl exec]]</code> | ||
* <code>[[kubectl attach]]</code> | * <code>[[kubectl attach]]</code> | ||
+ | * [[EKS troubleshooting]] | ||
== Activities == | == Activities == |
Revision as of 10:28, 26 February 2024
Commands
kubectl logs your_pod
kubectl get events -A
kubectl describe pod your_pod
kubectl describe nodes
, reviewconditions:
kubectl top
kubectl cluster-info dump
Events
- FailedScheduling:
Insufficient cpu
,Insufficient memory
,timed out waiting for the condition
,unbound immediate PersistentVolumeClaims
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
Kubernetes components
- Kubernetes scheduling
- Kubernetes Pod Topology Spread Constraints
- Kubernetes pod affinity and anti affinity
- Karpenter
ttlSecondsUntilExpired
,controller.node Triggering termination for expired node after 168h0m0s .../...
Log
Related
- Readiness, Liveness,
Readiness probe errored
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
Unable to connect to the server, ~/.kube/config
DiskPressure
CalculateExpectedPodCountFailed
aws eks create-cluster --logging
Node-pressure Eviction
karpenter.sh/do-not-evict: true
NodeNotReady
kubectl-node-shell
kubectl exec
kubectl attach
- EKS troubleshooting
Activities
- Review: https://learnk8s.io/troubleshooting-deployments
- Kubernetes debugging with an ephemeral debug container:
kubectl debug
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: