public:99_annexes:annex-b-terms-and-definitions:c:capability_image

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:c:capability_image [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:c:capability_image [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Capability Image ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Capability Image is a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|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 [[public:99_annexes:annex-b-terms-and-definitions:h:hardened_image|Hardened Image]] so that workload-specific functionality does not replace the shared operating-system and security foundation.
 +
 +===== Definition =====
 +
 +//[[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|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 artifact. A [[public:99_annexes:annex-b-terms-and-definitions:c:capability_layer|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.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>