Configuration Service
Deploy configuration-only services for feature flags and shared configuration
The configuration service type creates a configuration-only service that doesn’t deploy any containers. It’s useful for managing feature flags, shared configuration, or service metadata that other services can reference.
⚠️
This documentation is still in progress and will be updated shortly with the latest information.
Required Fields
| Field | Type | Description |
|---|---|---|
defaultTag | string | Configuration version tag |
branchName | string | Branch name for configuration source |
How It Works
A configuration service:
- Does not deploy any containers or pods
- Registers a service entry in Lifecycle for reference by other services
- Provides a way to version and track configuration changes
- Can be referenced by other services using template variables
Example
Use Cases
Feature Flags
Track feature flag configuration versions:
Shared Configuration
Reference shared configuration across services:
Environment Metadata
Track environment-specific metadata:
Configuration services are lightweight entries in Lifecycle’s service registry. They don’t consume cluster resources but allow other services to reference configuration state.