# Elasticsearch master cluster problem on kubernetes (installed via helm chart stable/elastic-stack)

**URL:** <https://discuss.elastic.co/t/elasticsearch-master-cluster-problem-on-kubernetes-installed-via-helm-chart-stable-elastic-stack/210127>\
**Category:** Elasticsearch\
**Created:** [December 2, 2019, 7:13am UTC](https://discuss.elastic.co/t/elasticsearch-master-cluster-problem-on-kubernetes-installed-via-helm-chart-stable-elastic-stack/210127 "2019-12-02T07:13:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon546463](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@anon546463](https://discuss.elastic.co/u/anon546463)\
**Post date:** [December 2, 2019, 7:13am UTC](https://discuss.elastic.co/t/elasticsearch-master-cluster-problem-on-kubernetes-installed-via-helm-chart-stable-elastic-stack/210127/1 "2019-12-02T07:13:02Z")

</div>

Hello,  
I've installed elastic-stack using command:

> helm upgrade --install elk-training stable/elastic-stack -f values.yaml

default elasticsearch settings:

> <https://github.com/helm/charts/blob/master/stable/elasticsearch/values.yaml>

values.yml:  
[http://dpaste.com/2KM8VGR](http://dpaste.com/2KM8VGR)

_kubectl get po,svc_

> NAME READY STATUS RESTARTS AGE  
> pod/elk-training-elasticsearch-client-585bc7f86b-2vg8f 0/1 Running 0 7m32s  
> pod/elk-training-elasticsearch-client-585bc7f86b-kb6g6 0/1 Running 0 7m32s  
> pod/elk-training-elasticsearch-data-0 0/1 Pending 0 7m32s  
> pod/elk-training-elasticsearch-master-0 1/1 Running 0 7m32s  
> pod/elk-training-elasticsearch-master-1 1/1 Running 0 6m4s  
> pod/elk-training-elasticsearch-master-2 1/1 Running 0 4m36s  
> pod/elk-training-kibana-7cf966746f-xv6vp 1/1 Running 0 7m32s
> 
> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE  
> service/elk-training-elasticsearch-client ClusterIP 10.233.9.172 9200/TCP 7m32s  
> service/elk-training-elasticsearch-discovery ClusterIP None 9300/TCP 7m32s  
> service/elk-training-kibana ClusterIP 10.233.46.32 443/TCP 7m32s  
> service/kubernetes ClusterIP 10.233.0.1 443/TCP 60d

_kubectl logs pod/elk-training-elasticsearch-client-585bc7f86b-kb6g6_  
[http://dpaste.com/2V06RM5](http://dpaste.com/2V06RM5)

_kubectl logs elk-training-elasticsearch-master-0_  
[http://dpaste.com/2BT63CG](http://dpaste.com/2BT63CG)

To me seems like Elasticsearch master is not elected, but i don't know the cause

---

<div class="post-metadata">

**Author:** ![anon546463](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@anon546463](https://discuss.elastic.co/u/anon546463)\
**Post date:** [December 5, 2019, 7:15am UTC](https://discuss.elastic.co/t/elasticsearch-master-cluster-problem-on-kubernetes-installed-via-helm-chart-stable-elastic-stack/210127/2 "2019-12-05T07:15:51Z")

</div>

Same issue with versions 7.5.0 (for Elasticsearch, Kibana and Logstash (Logstash is not enabled yet))

---

<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:** [January 2, 2020, 7:15am UTC](https://discuss.elastic.co/t/elasticsearch-master-cluster-problem-on-kubernetes-installed-via-helm-chart-stable-elastic-stack/210127/3 "2020-01-02T07:15:56Z")

</div>

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