dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003

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
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003 [2026/07/17 09:28] – nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003 [2026/07/30 05:46] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy a [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster]] to a target [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes clusters]].+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-003
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-003.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes clusters]].//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses a direct functional behavior but requires normative-language normalization and identification of the deployment target.+FR-DEP-003:
  
-The following Specification Discipline and Authoring findings apply:+  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] 
 +  * Changes **shall** to the established uppercase normative form **SHALL** 
 +  * Links **Kubernetes Clusters** to the controlling definition
  
-  * **The system** does not use the defined system name +No other substantive normalization is required.
-  * **shall** does not follow the established uppercase normative convention +
-  * **Kubernetes clusters** identifies the deployment subject but does not identify the target Infrastructure Environment +
-  * The source statement does not prescribe a Kubernetes distribution, topology, provider, installation mechanism, version, or implementation method +
-  * The source statement does not independently require cluster validation, workload deployment, rollback, or compliance assessment +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Retains the direct and testable verb **deploy** +
-  * Identifies a Kubernetes Cluster as the deployment subject +
-  * Identifies the target Infrastructure Environment +
-  * Preserves implementation independence +
-  * Retains one primary required behavior +
- +
-**Kubernetes Cluster** should receive a glossary definition because the term identifies a distinct deployable platform subject used by multiple requirements.+
  
 ===== Rationale ===== ===== Rationale =====
  
-A Kubernetes Cluster establishes the control-plane and worker-node capabilities used to schedule, execute, connect, and manage containerized workloads.+A [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Cluster]] provides the control-plane and worker-node capabilities required to schedule, execute, connect, and manage containerized workloads.
  
-A Kubernetes Cluster deployment may include:+Deploying Kubernetes Clusters enables Crucible to establish Kubernetes-based platforms through separately governed deployment workflows.
  
-  * Control-plane components +This requirement establishes Kubernetes Cluster deployment without prescribing:
-  * Worker nodes +
-  * Cluster networking +
-  * Cluster storage integration +
-  * Identity and access configuration +
-  * Security configuration +
-  * Service discovery +
-  * Admission controls +
-  * Monitoring integration +
-  * Logging integration+
  
-The applicable Infrastructure Configuration determines which components and values apply to a particular deployment.+  * A Kubernetes distribution 
 +  * A Kubernetes version 
 +  * A cluster topology 
 +  * The target Infrastructure Environment 
 +  * The Deployment Target 
 +  * The deployment mechanism 
 +  * Workload deployment 
 +  * Platform-service deployment 
 +  * Deployment validation 
 +  * Deployment rollback 
 +  * Compliance assessment
  
-Kubernetes Cluster deployment contributes to: +Separate requirements define those subjects and behaviors.
- +
-  * Repeatable container-platform establishment +
-  * Consistent cluster configuration +
-  * Automated platform creation +
-  * Portable workload hosting +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]+
  
 ===== Applies To ===== ===== Applies To =====
Line 72: Line 52:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * Kubernetes Clusters +  * [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]] 
-  * Kubernetes control-plane components +  * Kubernetes Cluster deployment operations
-  * Kubernetes worker nodes +
-  * Cluster networking +
-  * Cluster storage integration +
-  * Cluster identity and access configuration +
-  * Cluster security configuration +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]] +
-  * Kubernetes deployment workflows +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]+
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for a Kubernetes Cluster +Verification confirms that:
-  - Verification SHALL confirm that the deployment operation targets an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] +
-  - Verification SHALL confirm that the Kubernetes Cluster exists in the target Infrastructure Environment after successful deployment+
  
-Verification may include: +  - One or more Kubernetes Clusters are selected for deployment 
- +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for the selected Kubernetes Clusters 
-  * Kubernetes Cluster deployment testing +  - The completed deployment produces the selected Kubernetes Clusters 
-  * Kubernetes interface inspection +  - The resulting Kubernetes Clusters can be identified as outputs of the tested deployment
-  * Cluster-component inspection +
-  * Target-environment inspection +
-  * Deployment-output inspection +
-  * Deployment-log inspection +
-  * Automated CI/CD Pipeline testing +
- +
-The verification record SHALL identify: +
- +
-  - The deployed Kubernetes Cluster +
-  - The target Infrastructure Environment +
-  - The deployment operation +
-  - The deployment result +
-  - The observed cluster state +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-===== Outgoing Traceability ===== +
- +
-This requirement realizes: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001|MO-001]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002|MO-002]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003|MO-003]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006|MO-006]] +
- +
-This requirement relates to: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001|FR-DEP-001 — Deploy Infrastructure Resources]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004|FR-DEP-004 — Deploy Containerized Workloads]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005|FR-DEP-005 — Deploy Platform Services]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-006|FR-DEP-006 — Deployment Rollback]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-007|FR-DEP-007 — Deployment Validation]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-DEP-003''. +The following pages reference this requirement:
- +
-Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list. +
- +
-Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship. +
- +
-===== ConOps Relationship ===== +
- +
-The Crucible Concept of Operations describes automated platform and workload deployment through a Phase 1 CI/CD Pipeline. +
- +
-FR-DEP-003 establishes the required behavior for deploying a Kubernetes Cluster to a target Infrastructure Environment. +
- +
-Requirements governing infrastructure resources, containerized workloads, platform services, rollback, and validation define separate behavior. +
- +
-===== Delivery Phase =====+
  
-Phase 1+{{backlinks>.#dido:02-crusible}}
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +Implemented and Verified
- +
-Implementation status requires verification that Crucible deploys a Kubernetes Cluster to a target Infrastructure Environment.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and approve FR-DEP-003 as a leaf requirement.</todo>
- +
-The source System Requirements Specification identifies Version 1.1 as a draft.+
  
 ---- ----
-===== Notes for Editors =====+===== Issues =====
  
-This requirement page should retain the stable requirement identifier ''FR-DEP-003''.+<todo>Determine whether separate requirements identify the configuration used for each Kubernetes Cluster deployment.</todo>
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+<todo>Determine whether separate requirements identify the Deployment Target or Infrastructure Environment for each Kubernetes Cluster deployment.</todo>
  
-The Source Statement should preserve the original wording from the controlling System Requirements Specification.+---- 
 +===== Notes for Editors =====
  
-The Statement should remain limited to deployment of a Kubernetes Cluster.+This requirement page retains the stable requirement identifier ''FR-DEP-003''.
  
-Requirements for containerized workload deployment, platform services, rollback, validation, and cluster retirement should remain in their applicable requirement pages.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.+The Statement preserves the approved source intent by requiring Crucible to deploy Kubernetes Clusters.
  
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+Do not add a Kubernetes distribution, Kubernetes version, cluster topology, target Infrastructure Environment, Deployment Target, workload-deployment, platform-service, rollback, validation, compliance-assessment, or retirement obligation unless the controlling requirement changes through an approved requirements process.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
Line 182: Line 101:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003#Statement&noheader&nofooter&noeditbtn}}
 </code> </code>
- 
-Do not rename this page after an external citation unless a redirect or move plan is in place. 
  
 ---- ----
  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-03-deployment-orchestration/fr-dep-003.1784305700.txt.gz
  • Last modified: 2026/07/17 09:28
  • by nick_dido