Configuration Service
Deploy configuration-only Services for feature flags and shared configuration.
Use a configuration Service to make shared string values available to other
Services without deploying a container or pod.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
data | object of strings | Yes | Values added to the template environment |
branchName | string | No | Optional branch metadata |
Set data. You can set branchName. Do not set defaultTag because
Lifecycle rejects it. Before you push the file, run lfc schema validate lifecycle.yaml.
How it works
A configuration Service:
- Lifecycle does not deploy containers or pods for the Service.
- Lifecycle adds each
datakey to the template variables for other Services.
Lifecycle does not prefix configuration keys with the Service name. For
example, FEATURE_MODE becomes {{FEATURE_MODE}}.
Example
Typical tasks
Feature flags
Share feature switches with deployed Services:
Shared configuration
Make the same values available to multiple Services:
Environment metadata
Use shared data with built-in template variables:
Configuration Services do not consume workload resources.
Include the configuration Service in the Environment. Its data is then available during template rendering.