<p>How do I expose an ingress when running kubernetes with minikube in windows 10?</p>
<p>I have enabled the minikube ingress add on.</p>
<p>My ingress is running here...</p>
<pre><code>NAME               CLASS   HOSTS           ADDRESS        PORTS   AGE
helmtest-ingress   nginx   helmtest.info   192.168.49.2   80      37m
</code></pre>
<p>I have added my <code>hosts</code> entry...</p>
<pre><code>192.168.49.2 helmtest.info
</code></pre>
<p>I just get nothing when attempting to browse or ping either <code>192.168.49.2</code> or <code>helmtest.info</code></p>
<p>My ingress looks like the following</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: helmtest-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: helmtest.info
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: helmtest-service
                port:
                  number: 80
</code></pre>
<p>My service looks like the following...</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: v1
kind: Service
metadata:
  name: helmtest-service
  labels: 
    app: helmtest-service
spec:
  type: ClusterIP
  selector:
    app: helmtest
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
</code></pre>
<p>I can access my service successfully in the browser after running <code>minikube service helmtest-service --url</code></p>
<p>If I run <code>minikube tunnel</code> it just hangs here....</p>
<pre><code>minikube tunnel
❗  Access to ports below 1024 may fail on Windows with OpenSSH clients older than v8.1. For more information, see: https://minikube.sigs.k8s.io/docs/handbook/accessing/#access-to-ports-1024-on-windows-requires-root-permission
🏃  Starting tunnel for service helmtest-ingress.
</code></pre>
<p>Where am I going wrong here?</p>

<p>OP didn't provide further information so I will provide answer based on the current information.</p>
<p>You can run <code>Ingress</code> on <a href="https://minikube.sigs.k8s.io/docs/" rel="nofollow noreferrer">Minikube</a> using the <code>$ minikube addons enable ingress</code> command. However, ingress has more addons, like <a href="https://minikube.sigs.k8s.io/docs/handbook/addons/ingress-dns/" rel="nofollow noreferrer">Ingress DNS</a> using <code>minikube addons enabled ingress-dns</code>. In <code>Minikube</code> documentation you can find more details about this addon and when you should use it.</p>
<p>Minikube has quite a well described section about <a href="https://minikube.sigs.k8s.io/docs/commands/tunnel/" rel="nofollow noreferrer">tunnel</a>. Quite important fact about the tunnel is that it must be run in a separate terminal window to keep the LoadBalancer running.</p>
<blockquote>
<p>Services of type <code>LoadBalancer</code> can be exposed via the <code>minikube tunnel</code> command. It must be run in a separate terminal window to keep the <code>LoadBalancer</code> running. <code>Ctrl-C</code> in the terminal can be used to terminate the process at which time the network routes will be cleaned up.</p>
</blockquote>
<p>This part is described in <a href="https://minikube.sigs.k8s.io/docs/handbook/accessing/" rel="nofollow noreferrer">Accessing apps</a> documentation.</p>
<p>As OP mention</p>
<blockquote>
<p>I can access my service successfully in the browser after running minikube service helmtest-service --url</p>
<p>If I run minikube tunnel it just hangs here....</p>
</blockquote>
<p><strong>Possible Solution</strong></p>
<ul>
<li>You might use the old version of SSH, update it.</li>
<li>You are using ports &lt;1024. This situation it's described in <a href="https://minikube.sigs.k8s.io/docs/handbook/accessing/#access-to-ports-1024-on-windows-requires-root-permission" rel="nofollow noreferrer">this known issue</a> part. Try to use higher port like 5000 like in <a href="https://stackoverflow.com/questions/59994578/how-do-i-expose-ingress-to-my-local-machine-minikube-on-windows">this example</a></li>
<li>It might look like it just hangs, but you need a separate terminal window. Maybe it works correctly but you have to use another terminal</li>
</ul>
<p>Useful links</p>
<ul>
<li><a href="https://stackoverflow.com/questions/59994578/how-do-i-expose-ingress-to-my-local-machine-minikube-on-windows">How do I expose ingress to my local machine? (minikube on windows)</a></li>
<li><a href="https://stackoverflow.com/questions/58790433/">Cannot export a IP in minikube and haproxy loadBalancer - using minikube tunnel</a></li>
</ul>
