Dogfooding: Enable sudo access for Workspaces setup for internal team members

MR: Pending

Description

As part of Sudo access in a workspace (&13983 - closed) , we have released a new feature to enable secure sudo access in Workspace. This requires setup by the user on their Kubernetes cluster.

We want to enable this for our internal team members through the setup managed by groupdeveloper tooling.

Details about the steps can be seen here.

Acceptance Criteria

• Sudo access is available to users of internal setup of Workspaces on .com

Technical Requirements

As per the discussion bwlow, we will use sysbox for this, at the very least until we can use native kubernetes user namespacing on GKE.

As documented sysbox is the first choice. Its installation method seems to be more generic (daemonset on kubernetes cluster). Kata containers has cluster provider specific instructions.

Additionally, Contributor Success team uses Sysbox in their Workspaces setup without issues 🎉

Impact Assessment

Having the ability to sudo in workspaces would allow inspecting system logs and ease debugging improving the troubleshooting experience on remote development environments