<p>I followed <a href="https://docs.dask.org/en/latest/setup/kubernetes-helm.html#helm-install-dask-for-a-single-user" rel="nofollow noreferrer">these instructions</a> to deploy a Dask cluster on Kubernetes/Minikube with Helm. I installed and the deployed with the following command:</p>
<pre><code> helm install dask-chart dask/dask
</code></pre>
<p>Running <code>kubectl get services</code> I see the scheduler, however the EXTERNAL-IP is <code>none</code> and I cannot connect to the scheduler:</p>
<pre><code>NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)           AGE
dask-chart-scheduler   ClusterIP   10.107.222.251   &lt;none&gt;        8786/TCP,80/TCP   36m
</code></pre>
<p>What could be wrong here?</p>
<p><strong>UPDATE</strong></p>
<p>It's not only Dask, all the services have EXTERNAL-IP = none. I restarted Minikube but same problem persists.</p>

ps0604
<p>It is expected behavior if you use the service as <code>ClusterIP</code>. The meaning of <code>ClusterIP</code> is to let the service be accessible within the cluster. You should refer to this section from the official doc about the definition of <code>ClusterIP</code>, <a href="https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types</a>.</p>
<p>If you want to use the tunnel, you need to first set the service as <code>LoadBalancer</code>. Inside the minikube documentation, you can check out the full tutorial how you can access the apps inside the cluster, <a href="https://minikube.sigs.k8s.io/docs/handbook/accessing/#using-minikube-tunnel" rel="nofollow noreferrer">https://minikube.sigs.k8s.io/docs/handbook/accessing/#using-minikube-tunnel</a>.</p>
