Difference between revisions of "NodeNotReady"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
[[NodeReady]] | [[NodeReady]] | ||
[[context deadline exceeded]] | [[context deadline exceeded]] | ||
| + | [[UnAvailableLoadBalancer]] | ||
== See also == | == See also == | ||
Revision as of 16:51, 29 November 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
PLEG is not healthy NodeReady context deadline exceeded UnAvailableLoadBalancer
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:
