14.4 Container Runtime Configuration

Go To Top

Return to Containerisation

Containers should receive runtime Configuration through approved mechanisms, such as Configuration files, environment variables, command-line arguments, mounted volumes, or container orchestration settings.

Runtime Configuration should identify:

1. Node Identity.
2. Node Role.
3. Runtime profile.
4. DDS Configuration.
5. Topic Configuration.
6. QoS profile references.
7. Logging Configuration.
8. Input and output locations, where applicable.
9. Evidence or log export locations.
10. Required credentials or secret references, where applicable.

The team should distinguish Baseline Configuration from local overrides. Baseline Configuration should support repeatable execution. Local overrides should remain clearly marked and should not be entered into the controlled Baseline unless the team explicitly approves them.

Containers should not require developers to edit files inside a running container. Developers should modify Repository-controlled Configuration, rebuild the image where needed, and rerun the container through the approved scripts.