-
-
Notifications
You must be signed in to change notification settings - Fork 155
Closed as not planned
Description
I love the new setup for KubeCluster with the in-cluster Scheduler. We have the same usecase of wanting to run Dask jobs on remote K8s cluster from laptops and I pretty much have it running in the static version.
Our blocker for transitioning to KubeCluster is that we need to use Nodeports for accessing the scheduler, but our service accounts aren't allowed to have the "list node" privilege. Is there a way to pass in the IP to use for the scheduler, bypassing the NodePort lookup?