Difference between revisions of "KubeletReady"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* <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]] | ||
== Related == | == Related == | ||
Revision as of 17:21, 13 December 2022
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
Related
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:
