Technical Strategy for Self-Managed Runway

Context

Right now, Runway is an internal PaaS for GitLab team members to provision and deploy satellite services. The original problem the platform solves is enabling rapid innovation by deploying services to production on paved path. Based on company needs at the time, some components of the platform are tightly coupled to GitLab.com's internal infrastructure and GCP.

What

Create a technical strategy document to frame challenges and kick-off team discussions on Runway architecture using managed Kubernetes cluster control plane. The purpose of this document is to propose a plan for how to continue supporting the internal platform that currently serves GitLab team members, and provide recommendations for next steps to start the journey towards a platform that supports self-managed by design.

Why

By supporting self-managed installations, Runway can meet the company need of a platform that serves all GitLab product lines: self-managed (aka SM), multi-tenant (aka GitLab.com), and single tenant (aka Dedicated). For #407 (comment 2216172405).

References

Edited by Florian Forster