public:99_annexes:annex-b-terms-and-definitions:i:image_requirement

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:i:image_requirement [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:i:image_requirement to public:99_annexes:annex-b-terms-and-definitions:i:image_requirement nick_didopublic:99_annexes:annex-b-terms-and-definitions:i:image_requirement [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Image Requirement ====== ====== Image Requirement ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-An Image Requirement is a machine-processable statement that identifies a characteristic a [[private:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] must possess for a defined build, deployment, workload, or operating context.+An Image Requirement is a machine-processable statement that identifies a characteristic a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] must possess for a defined build, deployment, workload, or operating context.
  
 An Image Requirement may identify an operating-system family and version, processor architecture, capability, security posture, compliance profile, source revision, integrity value, provider compatibility, lifecycle status, or other selection criterion. An Image Requirement may identify an operating-system family and version, processor architecture, capability, security posture, compliance profile, source revision, integrity value, provider compatibility, lifecycle status, or other selection criterion.
Line 11: Line 11:
 Infrastructure can declare Image Requirements without identifying a specific Machine Image. An image-selection process compares those requirements with the characteristics recorded for available images. Infrastructure can declare Image Requirements without identifying a specific Machine Image. An image-selection process compares those requirements with the characteristics recorded for available images.
  
-Within Crucible, Image Requirements support separation between an [[private:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] and the Machine Images that may satisfy it.+Within Crucible, Image Requirements support separation between an [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] and the Machine Images that may satisfy it.
  
 ===== Definition ===== ===== Definition =====
  
-//machine-processable statement that identifies a characteristic a [[private:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] must possess for a defined build, deployment, workload, or operating context//+//machine-processable statement that identifies a characteristic a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] must possess for a defined build, deployment, workload, or operating context//
  
 ===== Source ===== ===== Source =====
Line 29: Line 29:
 ===== Example ===== ===== Example =====
  
-An Infrastructure Baseline declares Image Requirements for a [[private:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 AArch64 image with Kubernetes capability, an approved STIG compliance profile, and a verified integrity value.+An Infrastructure Baseline declares Image Requirements for a [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 AArch64 image with Kubernetes capability, an approved STIG compliance profile, and a verified integrity value.
  
 ---- ----
  • public/99_annexes/annex-b-terms-and-definitions/i/image_requirement.1789260153.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido