<p>Im trying to make an ingress for the minikube dashboard using the embedded dashboard internal service.</p>
<p>I enabled both <code>ingress</code> and <code>dashboard</code> minikube addons.</p>
<p>I also wrote this ingress YAML file :</p>
<pre><code>apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard-ingress
  namespace: kubernetes-dashboard
spec:
  rules:
  - host: dashboard.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: kubernetes-dashboard
            port: 
              number: 80
</code></pre>
<p>My Ingress is being created well as u can see :</p>
<pre><code>NAME                CLASS   HOSTS           ADDRESS     PORTS   AGE
dashboard-ingress   nginx   dashboard.com   localhost   80      15s
</code></pre>
<p>I edited my <code>/etc/hosts</code> to add this line : <code>127.0.0.1    dashboard.com</code>.</p>
<p>Now im trying to access the dashboard trough <code>dashboard.com</code>. But it's not working.</p>
<p><code>kubectl describe ingress dashboard-ingress -n kubernetes-dashboard</code> gives me this :</p>
<pre><code>Name:             dashboard-ingress
Namespace:        kubernetes-dashboard
Address:          localhost
Default backend:  default-http-backend:80 (&lt;error: endpoints &quot;default-http-backend&quot; not found&gt;)
Rules:
  Host           Path  Backends
  ----           ----  --------
  dashboard.com  
                 /   kubernetes-dashboard:80 (172.17.0.4:9090)
Annotations:     &lt;none&gt;
Events:
  Type    Reason  Age                From                      Message
  ----    ------  ----               ----                      -------
  Normal  Sync    14m (x2 over 14m)  nginx-ingress-controller  Scheduled for sync
</code></pre>
<p>I don't really understand what <code>&lt;error: endpoints &quot;default-http-backend&quot; not found&gt;</code> means, but maybe my issue comes from this.</p>
<p><code>kubectl get pods -n ingress-nginx</code> result :</p>
<pre><code>NAME                                        READY   STATUS      RESTARTS   AGE
ingress-nginx-admission-create--1-8krc7     0/1     Completed   0          100m
ingress-nginx-admission-patch--1-qblch      0/1     Completed   1          100m
ingress-nginx-controller-5f66978484-hvk9j   1/1     Running     0          100m
</code></pre>
<p>Logs for nginx-controller pod :</p>
<pre><code>-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:       v1.0.4
  Build:         9b78b6c197b48116243922170875af4aa752ee59
  Repository:    https://github.com/kubernetes/ingress-nginx
  nginx version: nginx/1.19.9

-------------------------------------------------------------------------------

W1205 19:33:42.303136       7 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1205 19:33:42.303261       7 main.go:221] &quot;Creating API client&quot; host=&quot;https://10.96.0.1:443&quot;
I1205 19:33:42.319750       7 main.go:265] &quot;Running in Kubernetes cluster&quot; major=&quot;1&quot; minor=&quot;22&quot; git=&quot;v1.22.3&quot; state=&quot;clean&quot; commit=&quot;c92036820499fedefec0f847e2054d824aea6cd1&quot; platform=&quot;linux/amd64&quot;
I1205 19:33:42.402223       7 main.go:104] &quot;SSL fake certificate created&quot; file=&quot;/etc/ingress-controller/ssl/default-fake-certificate.pem&quot;
I1205 19:33:42.413477       7 ssl.go:531] &quot;loading tls certificate&quot; path=&quot;/usr/local/certificates/cert&quot; key=&quot;/usr/local/certificates/key&quot;
I1205 19:33:42.420838       7 nginx.go:253] &quot;Starting NGINX Ingress controller&quot;
I1205 19:33:42.424731       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;ConfigMap&quot;, Namespace:&quot;ingress-nginx&quot;, Name:&quot;ingress-nginx-controller&quot;, UID:&quot;f2d27cc7-b103-490f-807f-18ccaa614e6b&quot;, APIVersion:&quot;v1&quot;, ResourceVersion:&quot;664&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/ingress-nginx-controller
I1205 19:33:42.427171       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;ConfigMap&quot;, Namespace:&quot;ingress-nginx&quot;, Name:&quot;tcp-services&quot;, UID:&quot;e174971d-df1c-4826-85d4-194598ab1912&quot;, APIVersion:&quot;v1&quot;, ResourceVersion:&quot;665&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/tcp-services
I1205 19:33:42.427195       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;ConfigMap&quot;, Namespace:&quot;ingress-nginx&quot;, Name:&quot;udp-services&quot;, UID:&quot;0ffc7ee9-2435-4005-983d-ed41aac1c9aa&quot;, APIVersion:&quot;v1&quot;, ResourceVersion:&quot;666&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/udp-services
I1205 19:33:43.622661       7 nginx.go:295] &quot;Starting NGINX process&quot;
I1205 19:33:43.622746       7 leaderelection.go:243] attempting to acquire leader lease ingress-nginx/ingress-controller-leader...
I1205 19:33:43.623402       7 nginx.go:315] &quot;Starting validation webhook&quot; address=&quot;:8443&quot; certPath=&quot;/usr/local/certificates/cert&quot; keyPath=&quot;/usr/local/certificates/key&quot;
I1205 19:33:43.623683       7 controller.go:152] &quot;Configuration changes detected, backend reload required&quot;
I1205 19:33:43.643547       7 leaderelection.go:253] successfully acquired lease ingress-nginx/ingress-controller-leader
I1205 19:33:43.643635       7 status.go:84] &quot;New leader elected&quot; identity=&quot;ingress-nginx-controller-5f66978484-hvk9j&quot;
I1205 19:33:43.691342       7 controller.go:169] &quot;Backend successfully reloaded&quot;
I1205 19:33:43.691395       7 controller.go:180] &quot;Initial sync, sleeping for 1 second&quot;
I1205 19:33:43.691435       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;Pod&quot;, Namespace:&quot;ingress-nginx&quot;, Name:&quot;ingress-nginx-controller-5f66978484-hvk9j&quot;, UID:&quot;55d45c26-eda7-4b37-9b04-5491cde39fd4&quot;, APIVersion:&quot;v1&quot;, ResourceVersion:&quot;697&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'RELOAD' NGINX reload triggered due to a change in configuration
I1205 21:06:47.402756       7 main.go:101] &quot;successfully validated configuration, accepting&quot; ingress=&quot;dashboard-ingress/kubernetes-dashboard&quot;
I1205 21:06:47.408929       7 store.go:371] &quot;Found valid IngressClass&quot; ingress=&quot;kubernetes-dashboard/dashboard-ingress&quot; ingressclass=&quot;nginx&quot;
I1205 21:06:47.409343       7 controller.go:152] &quot;Configuration changes detected, backend reload required&quot;
I1205 21:06:47.409352       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;Ingress&quot;, Namespace:&quot;kubernetes-dashboard&quot;, Name:&quot;dashboard-ingress&quot;, UID:&quot;be1ebfe9-fdb3-4d0c-925b-0c206cd0ece3&quot;, APIVersion:&quot;networking.k8s.io/v1&quot;, ResourceVersion:&quot;5529&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'Sync' Scheduled for sync
I1205 21:06:47.458273       7 controller.go:169] &quot;Backend successfully reloaded&quot;
I1205 21:06:47.458445       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;Pod&quot;, Namespace:&quot;ingress-nginx&quot;, Name:&quot;ingress-nginx-controller-5f66978484-hvk9j&quot;, UID:&quot;55d45c26-eda7-4b37-9b04-5491cde39fd4&quot;, APIVersion:&quot;v1&quot;, ResourceVersion:&quot;697&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'RELOAD' NGINX reload triggered due to a change in configuration
I1205 21:07:43.654037       7 status.go:300] &quot;updating Ingress status&quot; namespace=&quot;kubernetes-dashboard&quot; ingress=&quot;dashboard-ingress&quot; currentValue=[] newValue=[{IP: Hostname:localhost Ports:[]}]
I1205 21:07:43.660598       7 event.go:282] Event(v1.ObjectReference{Kind:&quot;Ingress&quot;, Namespace:&quot;kubernetes-dashboard&quot;, Name:&quot;dashboard-ingress&quot;, UID:&quot;be1ebfe9-fdb3-4d0c-925b-0c206cd0ece3&quot;, APIVersion:&quot;networking.k8s.io/v1&quot;, ResourceVersion:&quot;5576&quot;, FieldPath:&quot;&quot;}): type: 'Normal' reason: 'Sync' Scheduled for sync
</code></pre>
<p>Anyone has a clue on how i can solve my problem ?</p>
<p>(Im using minikube v1.24.0)</p>
<p>Regards,</p>

Fragan
<p>I have also faced the same issue with minikube(v1.25.1) running in my local.</p>
<p><code>kubectl get ingress -n kubernetes-dashboard</code></p>
<pre><code>NAME                CLASS   HOSTS           ADDRESS     PORTS   AGE
dashboard-ingress   nginx   dashboard.com   localhost   80      34m
</code></pre>
<p>After  debug I have found this.
&quot;If you are running Minikube locally, use minikube ip to get the external IP. The IP address displayed within the ingress list will be the internal IP&quot;.</p>
<p>Run this command</p>
<pre><code>minikube ip
XXX.XXX.64.2
</code></pre>
<p>add this ip in the host file,after that I am able to access dashboard.com</p>
