-
Notifications
You must be signed in to change notification settings - Fork 68
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
Integrate DLF into ODH JupyterHub #40
Comments
Thanks for moving this forward @vpavlin !
Regarding the labeling etc, the current way to mount in
Do you need a different functionality about the pods labeling convention? |
@YiannisGkoufas The labels should be fine, I would suggest to move the readonly up to |
Oh yes the |
Is there any progress on readonly access? |
Hey @vpavlin yes yes, not documented yet, but if you are feeling brave, try the following images for the dataset operator and csi-s3.
Example readonly dataset (only working on COS)
edit: removing the |
Hi @vpavlin can you check the branch https://github.com/IBM/dataset-lifecycle-framework/tree/readonly it support the readonly functionality in a Dataset as shown in the example |
Hi @YiannisGkoufas we are pushing a release of ODH and trying to finish some changes in JupyterHub, which is preventing me from looking at this. Just wanted to let you know this is still on the list for me! |
No worries @vpavlin ! thanks for letting me know. I have actually gathered some questions/ideas on ODH integration so would love discuss more when you have time |
Closing this issue as this is stale |
In opendatahub.io we use https://github.com/opendatahub-io/jupyterhub-singleuser-profiles to customize Jupyter instances for users.
I'd like to come up with a good integration between DLF and the profiles library.
As discussed with @YiannisGkoufas we would need to be able to mount volumes read-only too avoid users overwritting datasets for others
Then we could add a simple way to automatically label pods and add mounts to pods for users from a specific group
The text was updated successfully, but these errors were encountered: