Greetings, I am new to the Kubernetes world, so please forgive my ignorance. I am helping with a project that is using Jupyterhub to spawn notebooks for data analysis, and the project will likely acquire some hardware in the form of a few nodes. I am looking into adapting our Jupyterhub setup to use kubespawner <https://github.com/jupyterhub/kubespawner> in preparation for this.
I have been trying some tests on a small Kubernetes cluster I setup across two VMs. I've been attempting to follow the Zero to Jupyterhub <https://zero-to-jupyterhub.readthedocs.io/en/latest/> documentation, to get a vanilla test instance working. Currently, when I try to follow Zero to Jupyterhub, and deploy a test Jupyterhub + kubespawner setup using helm, I appear to get a volume mount error when it tries to spawn the hub pod. The VMs in my test kubernetes cluster have only local storage. Does there need to be some shared storage in order for the hub to function properly? I tried to turn off persistent user storage by setting singleuser: storagetype: none in the config.yaml file. I think I am somewhat misunderstanding the storage setup, and would appreciate any advice. In the future, we will need to replace the hub with a custom hub, which will perform certain custom actions on user login. Is there a list criteria (other than using kubespawner) that a hub must satisfy in order to work correctly with the Zero to Jupyterhub <https://github.com/jupyterhub/zero-to-jupyterhub-k8s> Kubernetes framework? Thanks much, Andrew Gustafson -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/e8859644-5819-4106-8923-a2b3042cd4c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
