Unhealthy

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

               "message": "(service your-service) (port 1236) is unhealthy in (target-group arn:aws:elasticloadbalancing:eu-west-1:***:targetgroup/your-tg/de945c5123456) due to (reason Health checks failed).", "id": "bab160d2-b5d5-4170-91a1-73e92f34b563", "createdAt": 1676632404.784

ECS

service your-service port 3000 is unhealthy in target-group your-tg  due to (reason Health checks failed with these codes: [404]).

Related

• kubectl get events -A | grep ClusterUnhealthy
• --kubelet-insecure-tls
• Reason
• FailedKillPod

See also

• kubectl describe pods
• 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