# Problems Installing Elasticsearch via Helm Kubernetes (version 7.6.1)

**URL:** <https://discuss.elastic.co/t/problems-installing-elasticsearch-via-helm-kubernetes-version-7-6-1/222610>\
**Category:** Elasticsearch\
**Created:** [March 8, 2020, 4:15pm UTC](https://discuss.elastic.co/t/problems-installing-elasticsearch-via-helm-kubernetes-version-7-6-1/222610 "2020-03-08T16:15:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![a\_pel73](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_pel73/32/48475_2.png) [@a\_pel73](https://discuss.elastic.co/u/a_pel73)\
**Post date:** [March 8, 2020, 4:15pm UTC](https://discuss.elastic.co/t/problems-installing-elasticsearch-via-helm-kubernetes-version-7-6-1/222610/1 "2020-03-08T16:15:51Z")

</div>

Hi, so I'm following the example to install [elasticsearch](https://github.com/elastic/helm-charts/tree/master/elasticsearch) via Helm chart.

I meet all the pre-requisite:

- Docker-for-Desktop Kubernetes: v1.10.11
- Helm v2.14.1

It doesn't appear all the pods are running and just stalls and never to ready state.

```auto
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 0/1 Running 0 19m
elasticsearch-master-1 0/1 Pending 0 19m
elasticsearch-master-2 0/1 Pending 0 19m
tiller-deploy-6b6684c87-nwpwm 1/1 Running 0 15h

```

getting the log for `kubectl log elasticsearch-master-0`

```auto
{"type": "server", "timestamp": "2020-03-08T15:43:57,731Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [elasticsearch-master-0, elasticsearch-master-1, elasticsearch-master-2] to bootstrap a cluster: have discovered [{elasticsearch-master-0}{XIUPmEuNSEKMP7mYrTPPYA}{t2F_bpO0SiyvlogO52pkjA}{10.1.1.62}{10.1.1.62:9300}{dilm}{ml.machine_memory=2147483648, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [] from hosts providers and [{elasticsearch-master-0}{XIUPmEuNSEKMP7mYrTPPYA}{t2F_bpO0SiyvlogO52pkjA}{10.1.1.62}{10.1.1.62:9300}{dilm}{ml.machine_memory=2147483648, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }

```

Note: Pulling Docker image elasticsearch image v7.6.1

---

<div class="post-metadata">

**Author:** ![Julien\_MAILLERET](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien_mailleret/32/45074_2.png) [@Julien\_MAILLERET](https://discuss.elastic.co/u/Julien_MAILLERET)\
**Post date:** [March 9, 2020, 7:57am UTC](https://discuss.elastic.co/t/problems-installing-elasticsearch-via-helm-kubernetes-version-7-6-1/222610/2 "2020-03-09T07:57:20Z")

</div>

Hi @a_pel73,  
Are you following [Docker for Mac example](https://github.com/elastic/helm-charts/tree/master/elasticsearch/examples/docker-for-mac)?  
Can you provide the exacte command and values file you are using?

---

<div class="post-metadata">

**Author:** ![a\_pel73](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_pel73/32/48475_2.png) [@a\_pel73](https://discuss.elastic.co/u/a_pel73)\
**Post date:** [March 12, 2020, 1:21am UTC](https://discuss.elastic.co/t/problems-installing-elasticsearch-via-helm-kubernetes-version-7-6-1/222610/3 "2020-03-12T01:21:34Z")

</div>

Hi, I didn't see the mac example....but I used the values file in there and seems to run unstable when viewing the data in Kibana but I tweak the ES memory value from 512M to 1024M and its running great! Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 9, 2020, 1:21am UTC](https://discuss.elastic.co/t/problems-installing-elasticsearch-via-helm-kubernetes-version-7-6-1/222610/4 "2020-04-09T01:21:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
