Difference between revisions of "Warning"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
kube-system 43m Warning [[ClusterUnhealthy]] configmap/cluster-autoscaler-status Cluster has no ready nodes. | 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) | ||
== Related == | == Related == | ||
Revision as of 13:06, 22 November 2022
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)
Related
kubectl get events -A | grep Normal
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:
