-
Notifications
You must be signed in to change notification settings - Fork 50
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
Jupyter notebook is not creating with volume set to ReadWriteMany #840
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5373.
|
This also happens on ReadOnlyMany volumes for notebooks |
@natalytvinova does it happen for ReadWriteOnce PVCs/volumes for notebooks? The problem above is that
The Notebook's pod has set |
From the K8s docs I see that
https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context So most probably this has to do with the StorageClass and kubelet is unable to change the GID of the mounted RWX PVC. So we'll need to better understand the storage provider, which in this case I understand it's Cinder |
Hi @kimwnasptd nope ReadWriteOnce volumes are okay Yes, in this case it is Cinder |
Adding more context here after some exploration. Also thanks to @addyess for his help looking through the CSI code and issues. First of all, Kubeflow Notebooks container https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context-1
The problem in this case is that upstream Cinder CSI driver does not support Lastly, for reference, our Charms that create the |
So what happens in this case is:
Since this is more of a problem of the underlying storage infrastructure not respecting K8s constructs, which Kubeflow relies on, I'll go on and close the issue since there's not much we can do from Kubeflow side |
Bug Description
While creating a Jupyter Notebook, I created a volume with the option "ReadWriteMany". The logs are in the end
The volume is created in the Kubernetes:
$ kubectl get pvc -A NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE admin uat-workspace Bound pvc-ae4e34b4-da07-4576-81b0-fd2a9c2a248a 20Gi RWX csi-cinder-default 13m $ kubectl get pv -A NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-ae4e34b4-da07-4576-81b0-fd2a9c2a248a 20Gi RWX Delete Bound admin/uat-workspace csi-cinder-default 13m
To Reproduce
Environment
Kubeflow bundle 1.8
Juju 3.1.7
Charmed Kubernetes 1.28
Kubernetes is on top of Openstack Yoga
Relevant Log Output
Additional Context
No response
The text was updated successfully, but these errors were encountered: