<p>I have minikube installed on Windows10, and I'm trying to work with <a href="https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/" rel="noreferrer">Ingress Controller</a></p>
<p>I'm doing:</p>
<blockquote>
<p>$ minikube addons enable ingress</p>
</blockquote>
<pre><code>* After the addon is enabled, please run &quot;minikube tunnel&quot; and your ingress resources would be available at &quot;127.0.0.1&quot;
  - Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
  - Using image k8s.gcr.io/ingress-nginx/controller:v0.44.0
  - Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
* Verifying ingress addon...
* The 'ingress' addon is enabled
</code></pre>
<blockquote>
<p>minikube addons list</p>
</blockquote>
<pre><code> minikube addons list
|-----------------------------|----------|--------------|
|         ADDON NAME          | PROFILE  |    STATUS    |
|-----------------------------|----------|--------------|
| ambassador                  | minikube | disabled     |
| auto-pause                  | minikube | disabled     |
| csi-hostpath-driver         | minikube | disabled     |
| dashboard                   | minikube | disabled     |
| default-storageclass        | minikube | enabled ✅   |
| efk                         | minikube | disabled     |
| freshpod                    | minikube | disabled     |
| gcp-auth                    | minikube | disabled     |
| gvisor                      | minikube | disabled     |
| helm-tiller                 | minikube | disabled     |
| ingress                     | minikube | enabled ✅   |
| ingress-dns                 | minikube | disabled     |
| istio                       | minikube | disabled     |
| istio-provisioner           | minikube | disabled     |
| kubevirt                    | minikube | disabled     |
| logviewer                   | minikube | disabled     |
| metallb                     | minikube | disabled     |
| metrics-server              | minikube | disabled     |
| nvidia-driver-installer     | minikube | disabled     |
| nvidia-gpu-device-plugin    | minikube | disabled     |
| olm                         | minikube | disabled     |
| pod-security-policy         | minikube | disabled     |
| registry                    | minikube | disabled     |
| registry-aliases            | minikube | disabled     |
| registry-creds              | minikube | disabled     |
| storage-provisioner         | minikube | enabled ✅   |
| storage-provisioner-gluster | minikube | disabled     |
| volumesnapshots             | minikube | disabled     |
|-----------------------------|----------|--------------|
</code></pre>
<p><strong>Note</strong>:
I ran <code>minikube tunnel</code> after the addon was enabled</p>
<p>But can't see the nginx controller anywhere:</p>
<blockquote>
<p>$ kubectl get pods -n kube-system</p>
</blockquote>
<pre><code>NAME                               READY   STATUS    RESTARTS   AGE
coredns-74ff55c5b-8gkwj            1/1     Running   0          2m35s
etcd-minikube                      1/1     Running   0          2m48s
kube-apiserver-minikube            1/1     Running   0          2m48s
kube-controller-manager-minikube   1/1     Running   0          2m48s
kube-proxy-jq4wm                   1/1     Running   0          2m35s
kube-scheduler-minikube            1/1     Running   0          2m48s
storage-provisioner                1/1     Running   2          2m47s
</code></pre>
<blockquote>
<p>$ kubectl get pods</p>
</blockquote>
<pre><code>No resources found in default namespace.
</code></pre>

zbeedatm
<p>As already discussed in the comments the Ingress Controller will be created in the <code>ingress-nginx</code> namespace instead of the <code>kube-system</code> namespace. Other than that the rest of the tutorial should work as expected.</p>
