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

Allow Jupyter pod to scale workers #87

Open
jacobtomlinson opened this issue Aug 6, 2020 · 1 comment
Open

Allow Jupyter pod to scale workers #87

jacobtomlinson opened this issue Aug 6, 2020 · 1 comment
Labels
chart/dask Related to the dask chart enhancement

Comments

@jacobtomlinson
Copy link
Member

Currently the Jupyter Notebook instance which is deployed as part of the helm chart can connect to the Dask cluster in order to use it, but it has no permissions on the Kubernetes cluster it is deployed on.

In dask/dask-kubernetes#255 we are adding a HelmCluster cluster manager which allows users to access logs and scale the workers deployed via the Helm Chart.

In order to use the cluster manager, you must have permissions to modify Deployment resources and access Pod log resources. It is assumed that those able to install the helm chart will have those permissions.

However if you deploy the helm chart and then make use of the provided Jupyter session then your credentials will not be available without some manual copying. Therefore the HelmCluster manager requires some additional configuration steps before it can work.

It could be helpful to include an optional service account in the helm chart which is made available to the Jupyter pod which has permission to scale the deployment and access logs.

cc @gforsyth @raybellwaves

@jacobtomlinson
Copy link
Member Author

When resolved this warning in dask-kubernetes should be updated.

@consideRatio consideRatio added the chart/dask Related to the dask chart label Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chart/dask Related to the dask chart enhancement
Projects
None yet
Development

No branches or pull requests

2 participants