<p>My issue is exactly the same as <a href="https://stackoverflow.com/questions/66275458/could-not-access-kubernetes-ingress-in-browser-on-windows-home-with-minikube">this</a>. But replication the question again for your reference::</p>
<p>I am facing the problem which is that I could not access the Minikube Ingress on the Browser using it's IP. I have installed Minikube on Windows 10 Home, and starting the minikube with docker driver(<code>minikube start --driver=docker</code>).</p>
<blockquote>
<p><strong>System info:</strong></p>
<p>Windows 10 Home</p>
<p>Minikube(v1.18.1)</p>
<p>Docker(driver for minikube) - Docker
engine version 20.10.5</p>
</blockquote>
<p>I am following this official document - <a href="https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/</a></p>
<p>First I created the deployment by running this below command on Minikube.</p>
<p><code>kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0</code></p>
<p>The deployment get created which can be seen on the below image: enter image description here</p>
<p><a href="https://i.stack.imgur.com/5byqt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5byqt.png" alt="enter image description here" /></a></p>
<p>Next, I exposed the deployment that I created above. For this I ran the below command.</p>
<p><code>kubectl expose deployment web --type=NodePort --port=8080</code></p>
<p>This created a service which can be seen by running the below command:</p>
<p><code>kubectl get service web</code>
The screenshot of the service is shown below:
<a href="https://i.stack.imgur.com/GkqAe.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/GkqAe.png" alt="enter image description here" /></a></p>
<ol start="3">
<li>I can now able to visit the service on the browser by running the below command:</li>
</ol>
<p><code>minikube service web</code></p>
<p>In the below screenshot you can see I am able to view it on the browser.</p>
<p><a href="https://i.stack.imgur.com/7760P.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/7760P.png" alt="enter image description here" /></a></p>
<ol start="4">
<li>Next, I created an Ingress by running the below command:</li>
</ol>
<p><code>kubectl apply -f https://k8s.io/examples/service/networking/example-ingress.yaml</code></p>
<p>The ingress gets created and I can verify it by running the below command:</p>
<p><code>kubectl get ingress</code>
The screenshot for this is given below:
<a href="https://i.stack.imgur.com/80QBA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/80QBA.png" alt="enter image description here" /></a></p>
<p>The ingress ip is listed as 192.168.49.2. So that means if I should open it in the browser then it should open, but unfortunately not. It is showing site can't be reached. See the below screenshot.</p>
<p><a href="https://i.stack.imgur.com/LeIOM.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/LeIOM.png" alt="enter image description here" /></a></p>
<p>What is the problem. Please provide me a solution for it?</p>
<p>I also added the mappings on etc\hosts file.</p>
<p><code>192.168.49.2 hello-world.info</code></p>
<p>Then I also tried opening hello-world.info on the browser but no luck.</p>
<p>In the below picture I have done ping to hello-world.info which is going to IP address 192.168.49.2. This shows etc\hosts mapping is correct:</p>
<p><a href="https://i.stack.imgur.com/OKGam.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/OKGam.png" alt="enter image description here" /></a></p>
<p>I also did curl to minikube ip and to hello-world.info and both get timeout. See below image:</p>
<p><a href="https://i.stack.imgur.com/yMML2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/yMML2.png" alt="enter image description here" /></a></p>
<p>The <code>kubectl describe services web</code> provides the following details:</p>
<pre><code>Name:                     web
Namespace:                default
Labels:                   app=web
Annotations:              &lt;none&gt;
Selector:                 app=web
Type:                     NodePort
IP:                       10.100.184.92
Port:                     &lt;unset&gt;  8080/TCP
TargetPort:               8080/TCP
NodePort:                 &lt;unset&gt;  31880/TCP
Endpoints:                172.17.0.4:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   &lt;none&gt;
</code></pre>
<p>The <code>kubectl describe ingress example-ingress</code> gives the following output:</p>
<pre><code>Name:             example-ingress
Namespace:        default
Address:          192.168.49.2
Default backend:  default-http-backend:80 (&lt;error: endpoints &quot;default-http-backend&quot; not found&gt;)
Rules:
  Host              Path  Backends
  ----              ----  --------
  hello-world.info
                    /   web:8080   172.17.0.4:8080)
Annotations:        nginx.ingress.kubernetes.io/rewrite-target: /$1
Events:             &lt;none&gt;
</code></pre>
<p><em><strong>The issue seems to have been resolved there</strong></em>, by following the below instructions(as posted in the comments):</p>
<blockquote>
<p>Once you setup the ingress with necessary change, i guess you are in
the powershell of windows with minikube running right? Make sure you
‘enable addons ingress’ and have a separate console running ‘minikube
tunnel’ as well. Also, add the hostname and ip address to windows’
host table. Then type ‘minikue ssh’ in powershell, it gives you
command line. Then you can ‘curl myapp.com’ then you should get
response as expected.</p>
</blockquote>
<p>Nevertheless, in my case, <em><strong>the minikube tunnel is not responding upon giving the <code>minikube tunnel</code> command.</strong></em> :</p>
<p><a href="https://i.stack.imgur.com/dVd3Z.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dVd3Z.png" alt="enter image description here" /></a></p>
<p><em><strong>I am not able to <code>curl hello-world.info</code> even through <code>minikube ssh</code>. Kindly help!</strong></em></p>

vagdevi k
<p><strong>On Windows</strong></p>
<p>After some decent amount of time, I came to the conclusion that ingress has some conflicts to work with Docker on Windows10-Home. Things are working fine if we want to expose a service of NodePort type but Ingress is troublesome.</p>
<p>Further, I tried to set up WSL 2 with Ubuntu in Windows 10 but no luck.</p>
<p>Finally, <strong>the following worked for Ingress of Minikube on Windows10 Home:</strong></p>
<ul>
<li>Install <a href="https://www.virtualbox.org/wiki/Downloads" rel="noreferrer">VirtualBox</a></li>
<li>Uncheck the <strong>Virtual Machine Platform</strong> and <strong>Windows Hypervisor Platform</strong> options from <code>Control Panel -&gt; Programs -&gt; Turn Windows Features on and off (under Programs and Features)</code> and then click ok. Restart your computer if prompted to.</li>
<li>Now, execute the following commands in a new cmd</li>
</ul>
<pre><code>minikube delete
minikube start --driver=virtualbox
</code></pre>
<p>if <code>minikube start --driver=virtualbox</code> doesn't work, then use <code>minikube start --driver=virtualbox --no-vtx-check</code>.</p>
<p>This process solved my problem and ingress is working fine on my Windows 10 Home Minikube.</p>
<p><strong>On Ubuntu</strong></p>
<p>Finally, Docker on Ubuntu is inherently supporting Minikube Ingress seamlessly without any glitch.</p>
