Skip to content
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

Merged
merged 6 commits into from
Feb 15, 2023
Merged

Conversation

olevski
Copy link
Member

@olevski olevski commented Jan 18, 2023

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:

  • Create a project which uses an image from the PR above
  • Add your public keys into the project at .ssh/authorized_keys
  • Start a session with an image that has a SSH server
  • Port forward to the jump host kubectl port-forward svc/renku-notebooks-ssh 2022:22
  • To access the session via SSH run 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

@olevski olevski requested review from a team as code owners January 18, 2023 12:49
@olevski olevski changed the title feat: ssh access to sessions feat: ssh access to sessions with jump host Jan 18, 2023
@olevski olevski marked this pull request as draft January 18, 2023 12:49
@Panaetius
Copy link
Member

Panaetius commented Jan 18, 2023

Port forward to the jump host kubectl port-forward svc/renku-notebooks-ssh 2022:22

is this just temporary until we can expose the port properly?

@olevski
Copy link
Member Author

olevski commented Jan 19, 2023

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.

Panaetius
Panaetius previously approved these changes Jan 19, 2023
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 January 26, 2023 12:24 — with GitHub Actions Inactive
@RenkuBot
Copy link
Contributor

You can access the deployment of this PR at https://renku-ci-nb-1389.dev.renku.ch

@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 January 27, 2023 10:11 — with GitHub Actions Inactive
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 January 27, 2023 10:55 — with GitHub Actions Inactive
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 January 27, 2023 15:56 — with GitHub Actions Inactive
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 January 27, 2023 17:18 — with GitHub Actions Inactive
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 February 6, 2023 08:59 — with GitHub Actions Inactive
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 February 6, 2023 11:15 — with GitHub Actions Inactive
@Panaetius Panaetius marked this pull request as ready for review February 14, 2023 12:57
@Panaetius Panaetius temporarily deployed to renku-ci-nb-1389 February 14, 2023 15:10 — with GitHub Actions Inactive
@Panaetius Panaetius deployed to renku-ci-nb-1389 February 15, 2023 13:31 — with GitHub Actions Active
@Panaetius Panaetius merged commit 556bfeb into master Feb 15, 2023
@Panaetius Panaetius deleted the feat-ssh-access branch February 15, 2023 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants