Difference between revisions of "Kubernetes troubleshooting"
Jump to navigation
Jump to search
Line 29: | Line 29: | ||
== See also == | == See also == | ||
+ | * {{kubectl get events}} | ||
* {{K8s troubleshooting}} | * {{K8s troubleshooting}} | ||
[[Category:K8s]] | [[Category:K8s]] |
Revision as of 15:05, 29 November 2022
kubectl logs your_pod
kubectl get events -A
kubectl describe pod your_pod
kubectl describe nodes
, review conditions:
kubectl top or K9s
Related
kubectl --cluster
- Kubernetes deployments
- Kubernetes components
- Readiness probe errored
- Readiness, Liveness
- BackOff
- BackoffLimitExceeded
- Type
- Reason: ProbeWarning
- Kubernetes Pod Disruptions
- NodeNotReady
Unable to connect to the server
Insufficient cpu Insufficient memory MemoryPressure DiskPressure
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: