K8s Elasticsearch with filebeat is keeping 'not ready' after rebooting K8s Elasticsearch with filebeat is keeping 'not ready' after rebooting kubernetes kubernetes

K8s Elasticsearch with filebeat is keeping 'not ready' after rebooting


Issue

There is an issue with elasticsearch readiness probe when running on single replica cluster.

Warning  Unhealthy               91s (x14 over 3m42s)  kubelet          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" )

Solution

As mentioned here by @adinhodovic

If your running a single replica cluster add the following helm value:

clusterHealthCheckParams: "wait_for_status=yellow&timeout=1s"

Your status will never go green with a single replica cluster.

The following values should work:

replicas: 1minimumMasterNodes: 1clusterHealthCheckParams: 'wait_for_status=yellow&timeout=1s'