The Elastic nodes are not able to start.

[ashishxooa]

The heathcheck and readiness probe is always failing for master and data node. Do they need more time to start?

es-data-efk-cluster-default-0 0/1 CrashLoopBackOff 5 14m
es-master-efk-cluster-default-0 0/1 CrashLoopBackOff 6 14m

Events from the pods.

  Warning  Unhealthy               7m12s                  kubelet, ip-172-20-35-37.ec2.internal  Liveness probe failed: Get http://100.96.3.157:9200/_nodes/_local: dial tcp 100.96.3.157:9200: connect: connection refused
  Normal   Pulled                  4m39s (x4 over 10m)    kubelet, ip-172-20-35-37.ec2.internal  Container image "quay.io/pires/docker-elasticsearch-kubernetes:6.4.2" already present on machine
  Normal   Created                 4m39s (x4 over 10m)    kubelet, ip-172-20-35-37.ec2.internal  Created container
  Normal   Started                 4m39s (x4 over 10m)    kubelet, ip-172-20-35-37.ec2.internal  Started container
  Warning  Unhealthy               4m19s (x6 over 7m12s)  kubelet, ip-172-20-35-37.ec2.internal  Readiness probe failed: dial tcp 100.96.3.157:9300: connect: connection refused

Nothing in the pod logs, just this.
➜ ~ kubectl logs es-master-efk-cluster-default-0
Starting Elasticsearch 6.4.2
Changing ownership of /data folder

Regards,
Ashish