[incubator/elasticsearch] master discovery not working in minikube

[AmazingTurtle]

Is this a request for help?:
Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-04-10T12:46:31Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Which chart:
incubator/elasticsearch

What happened:
elasticsearch client pod can not start:
not enough master nodes discovered during pinging (found [[]], but needed [1]), pinging again

What you expected to happen:
elasticsearch client pod starts sucecssfully

How to reproduce it (as minimally and precisely as possible):

$ minikube start --memory=8192 --cpus=4 --kubernetes-version=v1.10.0 --vm-driver hyperv --hyperv-virtual-switch "Extern"
$ helm init
$ helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
$ cat << EOF | kubectl apply -f -
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv0001-elasticsearch
spec:
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 30Gi
  hostPath:
    path: /data/pv0001/
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv0002-elasticsearch
spec:
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 4Gi
  hostPath:
    path: /data/pv0002/
EOF
$ helm install --name elasticsearch incubator/elasticsearch --set env.MINIMUM_MASTER_NODES=1 --set client.replicas=1 --set master.replicas=1 --set data.replicas=1 --set client.serviceType=NodePort

Anything else we need to know:

$ minikube addons list
- addon-manager: enabled
- coredns: disabled
- dashboard: enabled
- default-storageclass: enabled
- efk: disabled
- freshpod: disabled
- heapster: disabled
- ingress: enabled
- kube-dns: enabled
- registry: disabled
- registry-creds: disabled
- storage-provisioner: enabled

[AmazingTurtle]

I see this relates to another issue here
kubernetes/minikube#2302

Even though minikube addons list shows that kube-dns was enabled there were no pods. This might happened when doing minikube stop && minikube delete after enabling the addons.

[AmazingTurtle]

This has been a DNS issue. But there is another issue related to this. I will close this one and create a new issue (relate).