-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to set NodePort IP manually #348
Comments
There isn't a way to do this currently, but we could definitely add this. We would need a new config option which would make its way here and set the host instead of doing the lookup. dask-kubernetes/dask_kubernetes/utils.py Lines 56 to 57 in 6da9413
Do you have any interest in contributing this? |
Certainly, I'd love to give it a shot! |
The classic |
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?
The text was updated successfully, but these errors were encountered: