Difference between revisions of "KubeletReady"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
== Related == | == Related == | ||
* <code>[[kubectl get events -A]] | grep [[UnAvailableLoadBalancer]]</code> | * <code>[[kubectl get events -A]] | grep [[UnAvailableLoadBalancer]]</code> | ||
| − | * [[NodeNotReady]] | + | * <code>[[NodeNotReady]]</code> |
| − | * [[kubectl get nodes -o yaml]] | grep [[reason]] | + | * <code>[[kubectl get nodes -o yaml]] | grep [[reason]]</code> |
== Related == | == Related == | ||
Latest revision as of 12:26, 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[edit]
Kubelet conditions: MemoryPressure, DiskPressure, PIDPressure
Related[edit]
kubectl get events -A | grep UnAvailableLoadBalancerNodeNotReadykubectl get nodes -o yaml | grep reason
Related[edit]
See also[edit]
- 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:
