This is an old revision of the document!
10.5 Implementation Artefact / PSM to Deployment Artefact
An Implementation Artefact / PSM traces to a Deployment Artefact when a deployment profile describes how the implementation runs in a concrete environment.
For example, a container image may trace to a Kubernetes Deployment, Pod, or Helm chart. A DDS QoS profile may trace to a mounted configuration file or ConfigMap. A generated IDL binding may trace to a deployed service image using that binding.
This relationship supports operational review. It allows a reviewer to identify which deployed artefact executed, configured, exposed, or controlled a given implementation artefact.
Examples include:
Table 10.5-1: Examples of implementation artefacts traced to deployment artefacts
| Implementation Artefact / PSM | Deployment Artefact |
|---|---|
| OCI-compatible container image | Kubernetes Deployment, Pod, K3s workload, or local container runtime configuration |
| DDS Topic configuration | DDS XML configuration, mounted configuration file, or runtime topic registration |
| USER_QOS_PROFILES.xml | ConfigMap, mounted file, deployment package, or runtime configuration volume |
| Python Node implementation | Container entry point, process command, service manifest, or pod specification |
| Generated language binding | Built package, container layer, deployed runtime dependency, or generated source directory |
| Implementation configuration file | Environment-specific configuration file, ConfigMap, Secret, or mounted volume |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.