<p>I've setup a "hello world" ingress on Minikube as explained in <a href="https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/" rel="nofollow noreferrer">the tutorial</a>. The only difference - I removed the specific hostname to use '*' instead. However, it only seems to work with the ingress controller provided by minikube (<code>minikube addons enable ingress</code>). When I try to disable it and use <code>helm install nginx-ingress stable/nginx-ingress</code> instead, I can no longer access the Hello World sample website. I'm getting a "connection refused" error instead:</p>

<pre><code>$ kubectl get ingress
NAME              HOSTS   ADDRESS        PORTS   AGE
example-ingress   *       192.168.64.6   80      6m23s

$ minikube ip
192.168.64.6

$ curl -iv "192.168.64.6"
* Rebuilt URL to: 192.168.64.6/
* Hostname was NOT found in DNS cache
*   Trying 192.168.64.6...
* connect to 192.168.64.6 port 80 failed: Connection refused
* Failed to connect to 192.168.64.6 port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 192.168.64.6 port 80: Connection refused
</code></pre>

<p>If I switch back to the built-in addon, it works again:</p>

<pre><code>$ helm uninstall nginx-ingress
release "nginx-ingress" uninstalled

$ minikube addons enable ingress
✅  ingress was successfully enabled

$ curl -iv "192.168.64.6"
* Rebuilt URL to: 192.168.64.6/
* Hostname was NOT found in DNS cache
*   Trying 192.168.64.6...
* Connected to 192.168.64.6 (192.168.64.6) port 80 (#0)
&gt; GET / HTTP/1.1
&gt; User-Agent: curl/7.38.0
&gt; Host: 192.168.64.6
&gt; Accept: */*
&gt; 
&lt; HTTP/1.1 200 OK
HTTP/1.1 200 OK
* Server openresty/1.15.8.2 is not blacklisted
&lt; Server: openresty/1.15.8.2
Server: openresty/1.15.8.2
&lt; Date: Sun, 09 Feb 2020 07:06:58 GMT
Date: Sun, 09 Feb 2020 07:06:58 GMT
&lt; Content-Type: text/plain; charset=utf-8
Content-Type: text/plain; charset=utf-8
&lt; Content-Length: 59
Content-Length: 59
&lt; Connection: keep-alive
Connection: keep-alive

&lt; 
Hello, world!
Version: 1.0.0
Hostname: web-9bbd7b488-wsvsw
* Connection #0 to host 192.168.64.6 left intact
</code></pre>

<p>Is it possible to install to use this helm chart on minikube correctly?</p>

<p>I disabled ingress addon and installed nginx ingress with a helm chart you mentioned. I tested it and have a solution for you.</p>

<p>When you run:</p>

<pre><code>$ kubectl get services nginx-ingress-controller
</code></pre>

<p>you should see this output:</p>

<pre><code>NAME                       TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
nginx-ingress-controller   LoadBalancer   10.96.245.213   &lt;pending&gt;     80:30240/TCP,443:31224/TCP   50s
</code></pre>

<p>Notice that EXTERNAL-IP is in pending state.</p>

<p>minikube won't assign this IP by itself, you need to do it manually.</p>

<p>Run <code>kubectl edit svc nginx-ingress-controller</code> and add <code>externalIPs</code> field under <code>spec:</code> like following:</p>

<pre><code>spec:
  externalIPs:
  - 192.168.39.241 # minikube ip
</code></pre>

<p>Now let's see why this works.
Normally when running kubernetes in cloud environemnt when creating service of type LoadBalancer, cloud controller would create a load balancer and update the IP of the service, but because you are running it on minikube where no cloud specific features are working you need to add the address manually.</p>

<p>This can by any IP of any interface associated with your cluster so it should also work when having more nodes. You can add IP of any interface of your nodes and kuberentes will bind port on this interface and from now on you can send traffic to it and it will get forwarded to appropriate service/pod.</p>

<p>Let me know it it was helpful.</p>
