You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the Helm chart deployment's can work independently from each other and have just been bundled to reduce maintenance in the past. I'm not feeling fully confident that we should split them fully still, but I think we should in the long term. At this point in time I think we should work to make them as independent as we can without actually splitting them apart into two separate repositories, allowing us to do so in time.
The text was updated successfully, but these errors were encountered:
I think splitting them is the right ting to do. I'm not sure if they share the host private key now, but since these are two different services that will run on different ports, having them be separate is perhaps the right thing to do.
Kubernetes based deployment (jupyterhub ssh and/or sftp)
If your JupyterHub has been deployed to Kubernetes, you can use the Helm chart available in this repo to deploy JupyterHub SSH and/or JupyterHub SFTP directly into your Kubernetes cluster.
We currently maintain three things in one repo.
jupyterhub_ssh
Python package.jupyterhub-ssh
Helm chartjupyterhub-ssh
deploymentjupyterhub-sftp
deploymentBoth the Helm chart deployment's can work independently from each other and have just been bundled to reduce maintenance in the past. I'm not feeling fully confident that we should split them fully still, but I think we should in the long term. At this point in time I think we should work to make them as independent as we can without actually splitting them apart into two separate repositories, allowing us to do so in time.
The text was updated successfully, but these errors were encountered: