Deoploy Consul helm chart on minikube

[wrupertg]

Deploying default helm chart onto a blank minikube system has DNS issues.
minikube version: v0.28.2
kubernetes 1.10
helm version 2.10.0 (client and server)
MaxOS 10.13.6

Log output of first consul-server after launching it:
$ kubectl logs kissable-duck-consul-server-0
bootstrap_expect > 0: expecting 3 servers
==> Starting Consul agent...
==> Consul agent running!
Version: 'v1.2.3'
Node ID: '7a2aeb77-2b45-9c3b-0409-2b6612e949d1'
Node name: 'kissable-duck-consul-server-0'
Datacenter: 'dc1' (Segment: '')
Server: true (Bootstrap: false)
Client Addr: [0.0.0.0] (HTTP: 8500, HTTPS: -1, DNS: 8600)
Cluster Addr: 172.17.0.8 (LAN: 8301, WAN: 8302)
Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

2018/09/25 00:03:39 [INFO] raft: Initial configuration (index=0): []
2018/09/25 00:03:39 [INFO] raft: Node at 172.17.0.8:8300 [Follower] entering Follower state (Leader: "")
2018/09/25 00:03:39 [INFO] serf: EventMemberJoin: kissable-duck-consul-server-0.dc1 172.17.0.8
2018/09/25 00:03:39 [INFO] serf: EventMemberJoin: kissable-duck-consul-server-0 172.17.0.8
2018/09/25 00:03:39 [INFO] agent: Started DNS server 0.0.0.0:8600 (udp)
2018/09/25 00:03:39 [INFO] consul: Adding LAN server kissable-duck-consul-server-0 (Addr: tcp/172.17.0.8:8300) (DC: dc1)
2018/09/25 00:03:39 [INFO] consul: Handled member-join event for server "kissable-duck-consul-server-0.dc1" in area "wan"
2018/09/25 00:03:39 [WARN] agent/proxy: running as root, will not start managed proxies
2018/09/25 00:03:39 [INFO] agent: Started DNS server 0.0.0.0:8600 (tcp)
2018/09/25 00:03:39 [INFO] agent: Started HTTP server on [::]:8500 (tcp)
2018/09/25 00:03:39 [INFO] agent: started state syncer
2018/09/25 00:03:39 [INFO] agent: Retry join LAN is supported for: aliyun aws azure digitalocean gce k8s os packet scaleway softlayer triton vsphere
2018/09/25 00:03:39 [INFO] agent: Joining LAN cluster...
2018/09/25 00:03:39 [INFO] agent: (LAN) joining: [kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc]
2018/09/25 00:03:39 [WARN] memberlist: Failed to resolve kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
2018/09/25 00:03:39 [WARN] memberlist: Failed to resolve kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
2018/09/25 00:03:39 [WARN] memberlist: Failed to resolve kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
2018/09/25 00:03:39 [INFO] agent: (LAN) joined: 0 Err: 3 error(s) occurred:

• Failed to resolve kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
• Failed to resolve kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
• Failed to resolve kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
  2018/09/25 00:03:39 [WARN] agent: Join LAN failed: , retrying in 30s
  2018/09/25 00:03:44 [WARN] raft: no known peers, aborting election
  2018/09/25 00:03:46 [ERR] agent: failed to sync remote state: No cluster leader
  2018/09/25 00:04:07 [INFO] serf: EventMemberJoin: kissable-duck-consul-bqctk 172.17.0.7
  2018/09/25 00:04:09 [INFO] agent: (LAN) joining: [kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc]
  2018/09/25 00:04:09 [WARN] memberlist: Failed to resolve kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-1.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
  2018/09/25 00:04:09 [WARN] memberlist: Failed to resolve kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-2.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host
  2018/09/25 00:04:09 [INFO] agent: (LAN) joined: 1 Err:
  2018/09/25 00:04:09 [INFO] agent: Join LAN completed. Synced with 1 initial agents
  2018/09/25 00:04:13 [ERR] agent: Coordinate update error: No cluster leader
  2018/09/25 00:04:13 [ERR] agent: failed to sync remote state: No cluster leader
  2018/09/25 00:04:39 [ERR] agent: Coordinate update error: No cluster leader

Any ideas what is going wrong?

[mitchellh]

The core of it seems to be that the StatefulSet DNS names aren't resolving:

Failed to resolve kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc: lookup kissable-duck-consul-server-0.kissable-duck-consul-server.default.svc on 10.96.0.10:53: no such host

Is kube-dns configured?

[wrupertg]

When I deployed it with helm v2.11 it works fine