Skip to content
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

Closed
andersbogsnes opened this issue Jul 20, 2021 · 3 comments
Closed

Ability to set NodePort IP manually #348

andersbogsnes opened this issue Jul 20, 2021 · 3 comments

Comments

@andersbogsnes
Copy link
Contributor

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?

@jacobtomlinson
Copy link
Member

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.

nodes = await core_api.list_node()
host = nodes.items[0].status.addresses[0].address

Do you have any interest in contributing this?

@andersbogsnes
Copy link
Contributor Author

andersbogsnes commented Jul 20, 2021

Certainly, I'd love to give it a shot!

@jacobtomlinson
Copy link
Member

The classic KubeCluster was removed in #890. All users will need to migrate to the Dask Operator. Closing.

@jacobtomlinson jacobtomlinson closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants