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:
- Re-connect to workspaces without needing to go back to the Gitpod dashboard.
- 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.
JetBrains - Roadmap issue: #7956 Beta
- #11409 - Improve Git Integration validation by testing if host is reachable.
- #11400 - Switch to http/1.1 for gitlab.com repositories
- #11341 - [local-preview] show
DOMAINin the output
- #11237 - [kots]: add node CPU/memory check tests to workspace node only
- #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.
- #11208 - Users can see their billable sessions.
- #11205 - Minor fixes to the old Team Subscription UI
- #11192 - Make prebuild logs responsive for small viewports
- #11232 - Fix an issue that was causing the workspace to frequently timeout when using a JetBrains IDE.
- #11268 - [installer]: add test for customization of proxy service
- #379 - Fix
ports.onOpennot working on workspace startup
- #378 - Remove heartbeat in gitpod-remote VS Code plugin