Components
Components
Theseus is not a single project. It is the platform that emerges when these purpose-built components work together under a shared set of principles:
| Component | Role |
|---|---|
| Caproni | Local Kubernetes development environment |
| Runway | Abstraction, artifact generation, and orchestration |
| Fairway | Theseus’s Helm chart generator |
| LabKit | Standardised libraries for every GitLab service |
| Lab Bench | Service chassis and the bench CLI |
| common-template-copier | Project template that bootstraps every Theseus service |
| common-ci-tasks | Reusable CI components for build, test, lint, scan, and release |
| Release Framework | Canonical/security mirroring and release wiring for every project |
| Crete | Turnkey Self-Managed appliance: Talos, Flux, and the GitLab Operator with paved defaults |
| GitLab Operator | Installs, upgrades, and manages GitLab on customer Kubernetes and OpenShift |
| OAK | Omnibus Adjacent Kubernetes: Kubernetes-based install and operations delivered with Omnibus |
The GitLab Operator, Crete, and OAK are how Theseus covers installation and day-2 operations for Self-Managed customers: they consume the same artifacts every other environment runs. Fleet management of GitLab’s SaaS — rollout rings, progressive and A/B rollouts, maintenance windows, customer upgrade groupings — is not a Theseus concern; it belongs to Tenant Scale (GitLab.com and Cells) and the Dedicated team (Dedicated), who orchestrate what Theseus produces.
Last updated on