Cells
Theseus and Cells: separation of concerns
A new strategy page draws the line between the developer platform and the infrastructure architecture — what each owns, and the contract between them.
Platform bindings
One declarative interface, resolved per deployment target — and the rules for the Enterprise Platform Binding.
Pass application configuration via Fairway
Declare app config once in your Fairway manifest and let every environment deliver it — a ConfigMap in-cluster, a baked profile on Runway, per-cell values on Cells.
See what is running in production
Find the chart version and image running for your service on Runway, and where that answer lives for Cells.
Check pod health: restarts and probes
Count pod restarts, read probe failures, and hit your liveness and readiness endpoints for a Runway service. What exists per cell.
Operate
Running a modular feature in production: what is deployed, pod health, rolling and rolling back, safe rollout, configuration, and knowing which cell is affected. Built for the middle of an incident.
Roll a deployment
How a release reaches production on Runway, how to hold or release the production step, and who rolls a Cell.
Roll back a deployment
The fastest ways to get production back to the last good version on Runway, in order of speed, and what rollback means on a Cell.
Roll out new code safely
What the Runway Kubernetes runtime does and does not offer for progressive delivery, and how feature flags are the de-risking tool Theseus gives you.
Change configuration for a modular feature
Which file to edit for which environment, what ships a config change, what does not restart pods, and where per-cell values come from.
Know which cell is affected
Get SLO alerts for your Runway service, split them by region and cluster, and understand how a cell identifies itself in alerts today.
Feature Flag Strategy in Theseus
An overview of how feature flags will operate in Theseus for application developers
Modular feature test isolation
The strategy behind the default testing layer: test each modular feature against its contracts, with fakes for service dependencies, real infrastructure from Caproni, and no spun-up world.
Co-located Grafana dashboards
Dashboards are part of the service: jsonnet in the service repo, compiled in CI, shipped in the Helm chart, and discovered by whatever Grafana lives in the cell.
Metropolis: Monitoring as Part of the Service
SLIs, alerts, and dashboards declared as resources in the service repo, shipped with the chart, and compiled in-cluster by the GitLab Metrics Operator.
Separation of Concerns Between Theseus and Cells
Where the developer platform ends and the infrastructure architecture begins: what Theseus owns, what Cells owns, and the contract between them.