Configuration
Fairway services can now expose more than one port
A service that speaks gRPC to the cluster and HTTP to the world could not be expressed in a Fairway manifest. spec.listeners replaces spec.containerPort, and existing manifests keep working untouched.
Fairway v3.0.0: charts validate their own values
Every generated chart now ships a values.schema.json, so Helm rejects typo'd keys and out-of-range values before they reach a cluster — a breaking change worth reading before you regenerate.
The core contract
The separation of what software needs from how infrastructure provides it.
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.
Modify the values and secrets passed to your service
Practical examples for changing deploy-time values and Vault-backed secrets — none of which need an image rebuild.
Use feature flags in your service
Define a flag in the feature-flags repository, evaluate it with the LabKit client, toggle it with a merge request, and delete it when the rollout is done.
Fairway manifest schema
Field reference for the FairwayManifest declarative service interface.
Feature Flag Strategy in Theseus
An overview of how feature flags will operate in Theseus for application developers
Set up typed configuration
Simple protobuf-defined, validated application config with LabKit v2/config.