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

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

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

default elasticsearch settings:

values.yml:
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

kubectl logs elk-training-elasticsearch-master-0
http://dpaste.com/2BT63CG

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

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