Warning

kubectl get events -A | grep Warning

kube-system     43m         Warning   ClusterUnhealthy          configmap/cluster-autoscaler-status                     Cluster has no ready nodes.

monitoring      49m         Warning   Unhealthy                 pod/prometheus-blackbox-exporter-775954668d-49s4t       Readiness probe failed: Get "http://10.32.0.26:9115/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

23d         Warning   InvalidDiskCapacity       node/controlplane                      invalid capacity 0 on image filesystem

Related

kubectl get events -A | grep Normal
FailedMount

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