<p>I checked the previous question about this topic:
<a href="https://stackoverflow.com/questions/58561682/minikube-with-ingress-example-not-working">Minikube with ingress example not working</a><br>
But it doesn't solve my issue, since the solution doesn't work with newer version of <strong>Kubernetes</strong>. <em>Version 1.22</em><br>
<br></p>
<ul>
<li>The command I used:</li>
</ul>
<pre><code># Setup minikube
minikube start
minikube addons enable ingress

# Create the Deployment and Service
kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0;
kubectl expose deployment web --type=NodePort --port=8080;

# Create the Ingress
kubectl apply -f https://k8s.io/examples/service/networking/example-ingress.yaml;
</code></pre>
<p>Since I am using <strong>Minikube</strong> in local, I have to add the ip from <code>minikube ip</code> in the <code>etc/hosts</code>, which I did.</p>
<hr />
<h2>CHECKING:</h2>
<pre><code>❯ kubectl get all
NAME                       READY   STATUS    RESTARTS   AGE
pod/web-79d88c97d6-zfhgh   1/1     Running   0          24m

NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
service/kubernetes   ClusterIP   10.96.0.1      &lt;none&gt;        443/TCP          25m
service/web          NodePort    10.97.138.67   &lt;none&gt;        8080:31460/TCP   24m

NAME                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/web   1/1     1            1           24m

NAME                             DESIRED   CURRENT   READY   AGE
replicaset.apps/web-79d88c97d6   1         1         1       24m
</code></pre>
<p>We have the <strong>Pod</strong>, the <strong>Service</strong>, the <strong>Deployment</strong> and the <strong>RepicaSet</strong>.✅</p>
<pre><code>❯ kubectl get ingress
NAME              CLASS   HOSTS              ADDRESS        PORTS   AGE
example-ingress   nginx   hello-world.info   192.168.49.2   80      24m
</code></pre>
<p>The <strong>Ingress</strong> is okay, the address is indeed the <strong>Minikube</strong> IP. ✅</p>
<pre><code>❯ cat /etc/hosts
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateHosts = false
127.0.0.1       localhost
127.0.1.1       DESKTOP-B4JM855.localdomain     DESKTOP-B4JM855

192.168.1.12    host.docker.internal
192.168.1.12    gateway.docker.internal
127.0.0.1       kubernetes.docker.internal
192.168.49.2    hello-world.info        # &lt;----------- What we care about ✅ 

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
</code></pre>
<p>Everything should be correct but, I can't curl to the <strong>Ingress</strong> with:</p>
<blockquote>
<p>curl <a href="http://hello-world.info" rel="nofollow noreferrer">http://hello-world.info</a></p>
</blockquote>
<p>I do not know if using WSL is causing this issue, but it shouldn't be.</p>

Hamza Ince
<blockquote>
<p>Well, I tried coupal of things but none of them worked out well with <code>docker driver</code></p>
</blockquote>
<p>As of now, there is a going issue with <a href="https://github.com/kubernetes/ingress-nginx/issues/7686" rel="nofollow noreferrer">ingress doesn't work on docker desktop kubernetes</a></p>
<p>So you can't run ingress on local as of now with <code>docker Driver</code>. But you can try out this on AWS/IBM/GCP cloud and clear your task <a href="https://www.linkedin.com/pulse/deploying-aws-load-balancer-controller-ingress-eks-kai-jian-tan/" rel="nofollow noreferrer">link</a>.</p>
<blockquote>
<p>Alternatively, you can try with <code>hyperkit</code> <code>driver</code> like</p>
</blockquote>
<pre><code>minikube start --vm=true --driver=hyperkit
</code></pre>
<ul>
<li>Or Public Cloud (I tried and it worked) will be good choice to get it done fast.</li>
</ul>
