-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: ssh access to sessions with jump host #1389
Conversation
3df077e
to
bd7979d
Compare
bd7979d
to
7daf980
Compare
is this just temporary until we can expose the port properly? |
Yes. And exposing the port will only for dev.renku.ch and production deployments. Not every single CI or personal deployment. |
9c651e6
to
988bcae
Compare
You can access the deployment of this PR at https://renku-ci-nb-1389.dev.renku.ch |
dc8b873
to
1cba78d
Compare
f65b913
to
ffecdd5
Compare
ffecdd5
to
616e775
Compare
616e775
to
2d32456
Compare
2d32456
to
71bc109
Compare
71bc109
to
3cfc2a5
Compare
3cfc2a5
to
77c129f
Compare
Enables ssh access in notebooks via a jump host.
Depends on: SwissDataScienceCenter/renkulab-docker#291
It requires images from the PR above to be used in the session. Otherwise there is no ssh server in the session.
To test this do the following:
.ssh/authorized_keys
kubectl port-forward svc/renku-notebooks-ssh 2022:22
ssh -J jovyan@localhost:2022 jovyan@<session_id>
. The session id is the name of the JupyterServer resource in k8s. It is also in the url where you access the session in the browser./deploy #persist renku-core=feature/ssh-into-sessions extra-values=notebooks.ssh.enabled=true