←  Back to Changelog

July 18, 2022

Bring your own workspace SSH keys

SSH (secure shell) is a critical protocol for remote development. Both JetBrains IDEs and the VS Code editor use SSH as their remote development foundation. So, a big focus at Gitpod has been on improving performance and usability for connecting using SSH.

Which is why today we’re excited to announce that in Gitpod you can now upload your own public keys to access your workspace. In addition, we’ve also removed the requirement for a mandatory public key to be available when access Gitpod using SSH with an Access Token. With SSH public key upload you can now:

  1. Re-connect to workspaces without needing to go back to the Gitpod dashboard.
  2. Benefit from improved security when accessing your workspace with a private key.

See the announcement post for details on the use-cases, benefits and how to get started using your own key pair with Gitpod today.

@iqqbot's avatar on GitHub @mustard-mh's avatar on GitHub

Roadmap updates

JetBrains - Roadmap issue: #7956 Beta

  • #11209 - Add support for JetBrains Gateway v222.3345.1 and later. @akosyakov's avatar on GitHub @felladrin's avatar on GitHub @loujaybee's avatar on GitHub
  • #11307 - Gitpod Plugin for JetBrains IDEs was updated to respect network proxies. @akosyakov's avatar on GitHub @felladrin's avatar on GitHub

Fixes and improvements

Gitpod Core

  • #11409 - Improve Git Integration validation by testing if host is reachable. @AlexTugarev's avatar on GitHub @MrSimonEmms's avatar on GitHub @geropl's avatar on GitHub @jldec's avatar on GitHub
  • #11400 - Switch to http/1.1 for gitlab.com repositories @aledbf's avatar on GitHub @jenting's avatar on GitHub @kylos101's avatar on GitHub
  • #11341 - [local-preview] show DOMAIN in the output @Pothulapati's avatar on GitHub @adrienthebo's avatar on GitHub
  • #11237 - [kots]: add node CPU/memory check tests to workspace node only @MrSimonEmms's avatar on GitHub @lucasvaltl's avatar on GitHub @nandajavarma's avatar on GitHub
  • #11253 - Requests on ws-proxy won’t contain the port anymore on the “X-Forwarded-Host” header. It will contain only the host. If you need the port, you can get it from the “X-Forwarded-Port” header. @aledbf's avatar on GitHub @felladrin's avatar on GitHub
  • #11208 - Users can see their billable sessions. @andrew-farries's avatar on GitHub @laushinka's avatar on GitHub
  • #11205 - Minor fixes to the old Team Subscription UI @andrew-farries's avatar on GitHub @geropl's avatar on GitHub
  • #11192 - Make prebuild logs responsive for small viewports @andrew-farries's avatar on GitHub @geropl's avatar on GitHub @gtsiolis's avatar on GitHub @laushinka's avatar on GitHub
  • #11232 - Fix an issue that was causing the workspace to frequently timeout when using a JetBrains IDE. @akosyakov's avatar on GitHub @felladrin's avatar on GitHub @mustard-mh's avatar on GitHub
  • #11268 - [installer]: add test for customization of proxy service @MrSimonEmms's avatar on GitHub @nandajavarma's avatar on GitHub

Gitpod VSCode Browser

  • #379 - Fix .gitpod.yml ports.onOpen not working on workspace startup @jeanp413's avatar on GitHub @mustard-mh's avatar on GitHub
  • #378 - Remove heartbeat in gitpod-remote VS Code plugin @jeanp413's avatar on GitHub

Gitpod VSCode Desktop

  • #6 - Fix auth validation @jeanp413's avatar on GitHub
  • #5 - Use new getSSHPublicKeys api method @jeanp413's avatar on GitHub