Setup Cloud Sandbox Infrastructure for Workspaces
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Background
Following this discussion - https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/2818+, we need to establish dedicated development infrastructure for the Workspaces. This will replace our current shared development environment on GCP cluster gl-remote-dev-stg-0c1d2143 and provide isolated, secure infrastructure for Workspaces development, experimentation and debugging to replicate customer issues.
The current shared development infrastructure is experiencing:
- Performance issues due to resource competition from increased internal usage
- Potential security concerns with multiple teams using non-production infrastructure
- Limited computational resources
The Goal
The goal of this is to create a fully automated, Terraform-managed infrastructure setup that can be easily deployed by team members with minimal Kubernetes expertise. By developing comprehensive Terraform templates and clear documentation, we aim to enable any IC to spin up their own isolated development environment for use on .com with a simple terraform apply command - self-managed is out of scope.
This approach abstracts away the complexity of Kubernetes cluster management, networking, and agent configuration, making it accessible to developers who need to focus on maintaining or using Workspaces features rather than managing infrastructure. The solution will provide a reproducible, version-controlled infrastructure-as-code foundation while significantly lowering the barrier to entry for infrastructure provisioning.
Acceptance Criteria
-
Setup Workspaces Infrastructure in Cloud Sandbox - EM's account potentially. -
Create Terraform Template for Infrastructure setup -
Deploy and configure GitLab agent for Kubernetes -
Document the availability and usage instructions for other ICs and teams at GitLab who want to use Workspaces