<p>The whole cluster consists of 3 nodes and everything seems to run correctly:</p>
<pre><code>$ kubectl get pods --all-namespaces
NAMESPACE              NAME                                         READY   STATUS    RESTARTS        AGE
default                ingress-nginx-controller-5c8d66c76d-wk26n    1/1     Running   0               12h
ingress-nginx-2        ingress-nginx-2-controller-6bfb65b8-9zcjm    1/1     Running   0               12h
kube-system            calico-kube-controllers-684bcfdc59-2p72w     1/1     Running   1 (7d11h ago)   7d11h
kube-system            calico-node-4zdwr                            1/1     Running   2 (5d10h ago)   7d11h
kube-system            calico-node-g5zt7                            1/1     Running   0               7d11h
kube-system            calico-node-x4whm                            1/1     Running   0               7d11h
kube-system            coredns-8474476ff8-jcj96                     1/1     Running   0               5d10h
kube-system            coredns-8474476ff8-v5rvz                     1/1     Running   0               5d10h
kube-system            dns-autoscaler-5ffdc7f89d-9s7rl              1/1     Running   2 (5d10h ago)   7d11h
kube-system            kube-apiserver-node1                         1/1     Running   2 (5d10h ago)   7d11h
kube-system            kube-controller-manager-node1                1/1     Running   3 (5d10h ago)   7d11h
kube-system            kube-proxy-2x8fg                             1/1     Running   2 (5d10h ago)   7d11h
kube-system            kube-proxy-pqqv7                             1/1     Running   0               7d11h
kube-system            kube-proxy-wdb45                             1/1     Running   0               7d11h
kube-system            kube-scheduler-node1                         1/1     Running   3 (5d10h ago)   7d11h
kube-system            nginx-proxy-node2                            1/1     Running   0               7d11h
kube-system            nginx-proxy-node3                            1/1     Running   0               7d11h
kube-system            nodelocaldns-6mrqv                           1/1     Running   2 (5d10h ago)   7d11h
kube-system            nodelocaldns-lsv8x                           1/1     Running   0               7d11h
kube-system            nodelocaldns-pq6xl                           1/1     Running   0               7d11h
kubernetes-dashboard   dashboard-metrics-scraper-856586f554-6s52r   1/1     Running   0               4d11h
kubernetes-dashboard   kubernetes-dashboard-67484c44f6-gp8r5        1/1     Running   0               4d11h
</code></pre>
<p>The Dashboard service works fine as well:</p>
<pre><code>$ kubectl get svc -n kubernetes-dashboard
NAME                        TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
dashboard-metrics-scraper   ClusterIP   10.233.20.30   &lt;none&gt;        8000/TCP   4d11h
kubernetes-dashboard        ClusterIP   10.233.62.70   &lt;none&gt;        443/TCP    4d11h
</code></pre>
<p>What I did recently, was creating an Ingress to expose the Dashboard to be available globally:</p>
<pre><code>$ cat ingress.yml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard
spec:
  defaultBackend:
    service:
      name: kubernetes-dashboard
      port:
        number: 443
</code></pre>
<p>After applying the configuration above, it looks like it works correctly:</p>
<pre><code>$ kubectl get ingress
NAME        CLASS    HOSTS   ADDRESS   PORTS   AGE
dashboard   &lt;none&gt;   *                 80      10h
</code></pre>
<p>However, trying to access the Dashboard on any of the URLs below, both http and https, returns <code>Connection Refused</code> error:</p>
<pre><code>https://10.11.12.13/api/v1/namespaces/kube-system/services/kube-dns/proxy
https://10.11.12.13/api/v1/
https://10.11.12.13/
</code></pre>
<p>What did I miss in this configuration? Additional comment: I don't want to assign any domain to the Dashboard, at the moment it's OK to access its IP address.</p>

AbreQueVoy
<p>Ingress is <strong>namespaced</strong> resource , and kubernetes-dashboard pod located in &quot;kubernetes-dashboard&quot; namespace .</p>
<p>so you need to move the ingress to the &quot;kubernetes-dashboard&quot; namespace.</p>
<p>:: To list all namespaced k8s resources ::</p>
<pre><code>kubectl api-resources --namespaced=true
</code></pre>
