This is an old revision of the document!
Capability Image
Discussion
A Capability Image is a Machine Image that extends another image by adding a defined operational, platform, service, or workload capability.
The added capability may include software packages, runtime services, configuration, policies, agents, orchestration components, monitoring tools, or workload-specific dependencies.
A Capability Image preserves the inherited foundation of its source image while adding the elements needed for a particular role.
Within Crucible, a Capability Image may build on a Hardened Image so that workload-specific functionality does not replace the shared operating-system and security foundation.
Definition
machine image that extends another image by adding a defined operational, platform, service, or workload capability
Source
Generalized from layered-image, golden-image, virtual-appliance, platform-engineering, and machine-image usage and specialized for the Crucible architecture and operational model.
Note
A Capability Image identifies a realized image artefact. A Capability Layer identifies the controlled set of changes used to add the capability.
A Capability Image may provide one capability or a compatible combination of capabilities.
Example
Crucible adds Kubernetes packages, container-runtime services, node configuration, and cluster-management components to a Hardened Image. The resulting Capability Image supports deployment as a Kubernetes control-plane or worker node.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.