Deploying a secure Remote VSCode via open source code-server is seamless with Octelium. All you have to do is create a publicly exposed web-add Service whose upstream is the codercom/code-server
container image (read more about managed containers here). This can be done very easily as follows:
1kind: Service2metadata:3name: code4spec:5mode: WEB6isPublic: true7config:8upstream:9container:10port: 808011image: codercom/code-server:latest12args:13- --auth14- none15- --bind-addr16- 0.0.0.0:808017- --disable-getting-started-override18- --trusted-origins19- code.octelium.org20- --disable-workspace-trust21resourceLimit:22cpu:23millicores: 200024memory:25megabytes: 4000
Now you can access the Service publicly via the clientless/BeyondCorp using your browser at the address https://code.<DOMAIN>
. You can read more about publicly exposed BeyondCorp Services here.
You can also use and mount Kubernetes volumes to have persistent storage. Read more here
Another way is to use vanilla remote VSCode over SSH. In such case, you can define your own SSH
Service whose upstream can be any remote host, or even use the embedded SSH mode for VSCode. For example, you can run an octelium
client inside your Kubernetes cluster (read more here) that runs an embedded SSH server and from then use it as a remote host for VSCode. Here is an example (read more about deploying octelium
using Helm here):
helm install my-octelium-chart oci://ghcr.io/octelium/helm-charts/octelium --set octelium.domain=<DOMAIN> --set octelium.authToken=<AUTHENTICATION_TOKEN> --set "octelium.args={--essh}"
And now, from your own machine, connect to the Cluster with octelium connect
. If you embedded SSH Service has the hostname essh
then you just need to use the <SESSION_NAME>@essh
as the SSH address. You can read in detail on how to SSH into a specific host via embedded SSH here.