Difference between revisions of "NodeNotReady"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
[[PLEG is not healthy]] | [[PLEG is not healthy]] | ||
[[NodeReady]] | [[NodeReady]] | ||
| + | [[context deadline exceeded]] | ||
== See also == | == See also == | ||
Revision as of 16:47, 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
See also
- GKE, GKE Autopilot,
gcloud container, gke-gcloud-auth-plugin, GKE release channels, GKE Ingress, GCP Node logs, GCP Node logs severity Error, GKE roles, Provide access to GKE cluster, Deploy GKE cluster using Terraform,cluster_autoscaling, addons_config, GKE Node Pool, node auto-provisioning - 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:
