What Happened?

When in multi-node cluster mode the ingress-dns pod is not scheduled on the primary node leading to the errors setting up on the get started guide.

Steps to reproduce:

1. minikube start -n 3 --addons=ingress,ingress-dns
2. follow the steps in the ingress-dns guide
3. do a dns lookup on the running service nslookup hello-jane.test $(minikube ip)

Expected: the nslookup succeeds
Actual: the dns lookup fails with communication error: connection refused.

Attach the log file

N/A

Operating System

Ubuntu

Driver

Docker