Expose workspace ports on external IP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Currently the model we use for accessing workspace ports is different to 'real' machines our users are used to.
Problems with this approach:
- limited to
https - a lot of frontends try to connect to backends using the pattern
${window.location.hostname}:${port}, which does not work with Gitpod (example: https://github.com/gitpod-io/gitpod/issues/435#issuecomment-480750205 f). Only solution: patch the respective code or put proxy in front
A solution would be to expose workspaces under a IP6 address. Then each workspace would be accessible under: :
Optionally, we could add a (customizable) DNS entry for that as well (see #329)
This would allow other usecases:
sshaccess into workspaces to integrate with local environment- none-https traffic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's current workspace-port model, the linked discussion in #435, and the related DNS proposal in #329. Done would mean exposing workspace ports through an external IPv6 address, with optional DNS support, so SSH and non-HTTPS traffic can work without frontend-specific proxying.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100