Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
(→Log) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 36: | Line 36: | ||
== Log == | == Log == | ||
| − | * [[Karpenter logs]] | + | * <code>[[Karpenter logs]]</code> |
| − | * [[Kubelet logs]] | + | * <code>[[Kubelet logs]]</code> |
* <code>[[/var/log/kubelet.log]]</code> | * <code>[[/var/log/kubelet.log]]</code> | ||
== Related == | == Related == | ||
* [[Readiness]], [[Liveness]], <code>[[Readiness probe errored]]</code> | * [[Readiness]], [[Liveness]], <code>[[Readiness probe errored]]</code> | ||
| − | * [[Reason]]: [[ProbeWarning]] | + | * <code>[[Reason]]: [[ProbeWarning]]</code> |
* [[Kubernetes Pod Disruptions]] | * [[Kubernetes Pod Disruptions]] | ||
* <code>[[Unable to connect to the server]], [[~/.kube/config]]</code> | * <code>[[Unable to connect to the server]], [[~/.kube/config]]</code> | ||
Latest revision as of 11:55, 28 February 2024
Commands[edit]
kubectl logs your_podkubectl get events -Akubectl describe pod your_podkubectl describe nodes, reviewconditions:kubectl topkubectl cluster-info dump
Events[edit]
- 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[edit]
- 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[edit]
Related[edit]
- 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: trueNodeNotReadykubectl-node-shellkubectl execkubectl attach- EKS troubleshooting
Activities[edit]
- Review: https://learnk8s.io/troubleshooting-deployments
- Kubernetes debugging with an ephemeral debug container:
kubectl debug
See also[edit]
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:
