Difference between revisions of "NodeNotReady"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
== Related == | == Related == | ||
| + | * <code>[[NodeReady]]</code> | ||
* <code>[[kubectl describe nodes]]</code> | * <code>[[kubectl describe nodes]]</code> | ||
* <code>[[PLEG is not healthy]]</code> | * <code>[[PLEG is not healthy]]</code> | ||
| − | |||
* <code>[[context deadline exceeded]]</code> | * <code>[[context deadline exceeded]]</code> | ||
* <code>[[UnAvailableLoadBalancer]]</code> | * <code>[[UnAvailableLoadBalancer]]</code> | ||
Revision as of 10:55, 16 December 2022
kubectl get events -A default 60m Normal NodeReady node/gke-gitlab-runner-cluster-pool-3-5b68f91c-1234 Node gke-gitlab-runner-cluster-pool-3-5b68f91c-1234 status is now: NodeReady
Related
NodeReadykubectl describe nodesPLEG is not healthycontext deadline exceededUnAvailableLoadBalancer
See also
- Kubernetes nodes,
node.kubernetes.ioK8s Node controller (node-controller),MemoryPressure, DiskPressure, NodeHasDiskPressure, events, NodeNotReady, Node-pressure Eviction, RemovingNode, ProviderID,kubectl node-shell, kubectl describe nodes 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:
