Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
| Line 37: | Line 37: | ||
* <code>[[aws eks create-cluster --logging]]</code> | * <code>[[aws eks create-cluster --logging]]</code> | ||
* <code>[[Node-pressure Eviction]]</code> | * <code>[[Node-pressure Eviction]]</code> | ||
| − | |||
| − | |||
* <code>[[karpenter.sh/do-not-evict: true]]</code> | * <code>[[karpenter.sh/do-not-evict: true]]</code> | ||
* [[Kubernetes troubleshooting steps]] | * [[Kubernetes troubleshooting steps]] | ||
Revision as of 19:26, 19 January 2023
Commands
kubectl logs your_podkubectl get events -Akubectl describe pod your_podkubectl describe nodes, reviewconditions:
- Tools:
kubectl top,K9sandcrictl
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
Related
- Readiness, Liveness,
Readiness probe errored - Reason: ProbeWarning
- Kubernetes Pod Disruptions
Unable to connect to the server, ~/.kube/configDiskPressureCalculateExpectedPodCountFailedaws eks create-cluster --loggingNode-pressure Evictionkarpenter.sh/do-not-evict: true- Kubernetes troubleshooting steps
Activities
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:
