Difference between revisions of "KubeletReady"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
* <code>[[kubectl get events -A]] | grep [[UnAvailableLoadBalancer]]</code> | * <code>[[kubectl get events -A]] | grep [[UnAvailableLoadBalancer]]</code> | ||
* [[NodeNotReady]] | * [[NodeNotReady]] | ||
| − | * [[kubectl get nodes -o yaml]] | grep [[reason]] | + | * <code>[[kubectl get nodes -o yaml]] | grep [[reason]]</code> |
== Related == | == Related == | ||
Revision as of 12:05, 13 November 2023
kubectl describe nodes | grep KubeletReady Ready True Tue, 29 Nov 2022 16:18:40 +0100 Tue, 29 Nov 2022 15:18:04 +0100 KubeletReady kubelet is posting ready status. AppArmor enabled
Contents
Kubelet conditions
Kubelet conditions: MemoryPressure, DiskPressure, PIDPressure
Related
kubectl get events -A | grep UnAvailableLoadBalancer- NodeNotReady
kubectl get nodes -o yaml | grep reason
Related
See also
- 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:
