-
I've been experimenting with installing coder on kubernetes. It's unclear to me what the expectation is for setting CODER_ACCESS_URL to allow users to ssh into workspace pods. If I install coder via the helm chart and set no CODER_ACCESS_URL then I can get to the UI via the external IP of the load balancer service and successfully start simple workspaces. I can also use the CLI against that external IP. However, when I try to ssh into the workspaces using the coder ssh config the ssh command simply hangs. Looking at the workspace pods I can see they connect to the coder server via the load balancer service local cluster name, which makes sense to me. I can only manage to ssh into the workspace pods if I upgrade the helm deployment with CODER_ACCESS_URL set to the load balancer external IP so that the worker pods are also using that IP to connect to the coder server. It confuses me if this is intentional or not? What am I supposed to do if the external load balancer IP isn't accessible by the pods? For example, If I create a private kubernetes cluster with public access only via a bastion host, the pods will have to connect to the coder server via the local service name, which just causes ssh connections to hang. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
https://coder.com/docs/v2/latest/admin/configure#access-url |
Beta Was this translation helpful? Give feedback.
You can use an internal service name for specific templates. Here are the docs. However, each workspace will need some way to reach the Coder dashboard URL.