Open consideRatio opened 3 years ago
We should definitely disable SFTP by default!
The PVC is usually the same PVC used by JupyterHub - so it needs to be ReadWriteMany. As such, I think Deployment is more appropriate. What do you think?
This definitely needs some, any documentation :'(
Hi @yuvipanda and @consideRatio
Just wondering if either of you found a solution to the issue with the error message:
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Deployment.spec.template.spec.volumes[0].persistentVolumeClaim): missing required field "claimName" in io.k8s.api.core.v1.PersistentVolumeClaimVolumeSource
I'm really keen to be able to use the tool, but I know very little about K8s so struggling to work around the issues I'm having with this.
Thanks!
I know the feeling @glsdown, when I started learning about k8s I was a high school teacher trying to make JupyterHub available to my students :)
@glsdown using helm
you can configure values that influence how templates of k8s manifests are rendered. In this case, you should configure...
# my-config.yaml, passed to "helm upgrade" as "--values my-config.yaml"
sftp:
enabled: false
Note that if you want to use the sftp
functionality that is enabled by default but requires configuration of sftp.pvc.name
, it becomes more complicated and I won't try address that in this answer.
Thanks @consideRatio
I’ve jumped in at the deep end rather with all this, so very grateful for you taking the time to respond.
The SFTP part of the Helm chart is enabled by default.
https://github.com/yuvipanda/jupyterhub-ssh/blob/69a5bb08e199295748d2dc277d66a7e9001b0b76/helm-chart/jupyterhub-ssh/values.yaml#L50-L57
Also, it requires a PVC claimName to be explicitly set by default, otherwise, a user will experience the following error during
helm install
when the rendered Helm templates fail validation with the k8s api-server because of a empty string as a PVC claimName.Suggestions