Allow configuration of connect via SSH port (e.g. port 22)

[mrsimonemms]

Is your feature request related to a problem? Please describe

The "connect [to workspace] via SSH" button only connects via port 22.

When using k3s on a plain VM, some vendors (eg, Hetzner/DigitalOcean/Civo) don't provide an option to change the port for SSHing into the VM. This means that they can never enable the "connect via SSH" option on their Gitpod installation.

Describe the behaviour you'd like

An option in the KOTS dashboard to configure the SSH port to a different port number. This would need changes in the Installer and server components to handle this configuration parameter.

Describe alternatives you've considered

Without the option to configure the SSH port on the machine, there are limited available options.

Additional context

In the KOTS dashboard at least, we may wish to offer a select list of available ports to avoid internal port conflicts - suggest 22 (default), 2200, 2222, and 2244. The Installer and server should just accept the value that they are given.

Internal discussion

[mrsimonemms]

Based on #10643 (comment), I think that bumps up the priority on this ticket to being a dependency.

If I'm reading it correctly, that also means that the KOTS dashboard needs to always allow login via SSH as it becomes necessary

cc @loujaybee

[mrsimonemms]

See also https://github.com/gitpod-io/website/issues/2238

[loujaybee]

Noting that this looks related / similar to: #7452

UPDATE:

The following isse:

• Workaround for users who cannot use port 22 / SSH (e.g. SSH over HTTPS) #7452

Is to find a solution for users in SaaS where no access to installation is given. Whereas this issue should be scoped to an installation level fix, where access to port configurations is possible.

[loujaybee]

Removing WebApp project from this issue, as seems more IDE and Self-Hosted 🙏

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tyler36]

Would love to see some progress on this issue. Our IT department blocks access to port 22 unless you submit an application the day before.

[mrsimonemms]

Hey @tyler36 - Gitpod self-hosted is dead.

That said, I did figure out a way how to change the server's port 22 to 2244 - this doesn't affect Gitpod's SSH server running on port 22 and, as self-hosted is dead, I sincerely doubt it will.

[akosyakov]

@tyler36 you can switch to Web tunnel via gitpod.remote.useLocalApp: true in VS Code user settings. We are also working on new smoother experience which will automatically find the best way to connect, stay tune!

[tyler36]

@akosyakov

if I set gitpod.remote.useLocalApp: true, it overrides remote.SSH.configFile on my local PC which means I have manually change it back before I can access other SSH remotes.

[akosyakov]

yeah, sorry, for now we don't have the better way, we are working on new which should not, but still in prototype state