Fix workspaces SSH port on MacOS
What does this MR do and why?
For some reason, workspaces SSH support stopped working in local MacOS development environment.
This happened sometime around Jan 2025. @cwoolley-gitlab first encountered it, and @vtak verified on his machine.
The fix in this MR is to update the scripts/remote_development/workspaces_kubernetes_setup.sh script to override the gitlab-workspaces-proxy helm chart to listen for SSH connections on port 30022 instead of port 22.
Not sure what the root cause is, here's current versions where this is occurring:
- MacOS:
15.2 (24C101) - Rancher Desktop:
1.13.1 - Kubernetes:
1.29.5
The behavior was inconsistent, on Chad's machine SSH would connect but fail to accept a valid token as password. On Vishal's machine it wouldn't even connect.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
-
Change port in script -
Update https://gitlab.com/gitlab-org/workspaces/gitlab-workspaces-docs/-/blob/main/doc/ssh.md to show command with non-default port -
Update https://gitlab.com/gitlab-org/workspaces/gitlab-workspaces-proxy#step-5-install-helm-chart to add helm chart option to example
Screenshots or screen recordings
N/A
How to set up and validate locally
With local workspaces installed, run scripts/remote_development/workspaces_kubernetes_setup.sh then verify you can connect to a workspace via SSH over port 30022.