Difference between revisions of "Unhealthy"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
== Related == | == Related == | ||
* <code>[[kubectl get events -A]] | grep [[ClusterUnhealthy]]</code> | * <code>[[kubectl get events -A]] | grep [[ClusterUnhealthy]]</code> | ||
| + | * <code>[[--kubelet-insecure-tls]]</code> | ||
== See also == | == See also == | ||
Revision as of 14:22, 7 December 2022
kubectl get events -A | grep Warning kubectl describe pods | grep Unhealthy
your_namespace 26m Warning Unhealthy pod/elasticsearch-master-1 Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )...
Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )
kube-system 42m Warning Unhealthy pod/tiller-deploy-68bb9fb75-kw5r5 Liveness probe failed: Get "http://10.32.0.15:44135/liveness": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
13s Warning Unhealthy pod/metrics-server-7f4db5fd87-5lwkg Readiness probe failed: HTTP probe failed with statuscode: 500
Reason
FailedKillPod
Related
See also
- 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:
