FR-DEP-004 — Deploy Containerized Workloads

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL deploy a Containerized Workloads.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-004.

Assessment

The source statement expresses a direct functional behavior but requires normative-language normalization and identification of the deployment target.

The following Specification, Discipline, and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionContainerized workloads identify the deployment subject but do not identify the target platformThe source statement does not prescribe a container runtime, orchestration platform, Container Image format, provider, or deployment methodThe source statement does not independently require workload validation, availability, scaling, rollback, or compliance assessmentThe normalized Statement:

Replaces The system with CrucibleRetains the direct and testable verb deployIdentifies a containerized workload as the deployment subjectIdentifies a target container platformPreserves implementation independenceRetains one primary required behaviorContainerized Workload and Container Platform should receive glossary definitions because they identify distinct architectural subjects used by this and related requirements.

Rationale

A containerized workload comprises one or more container instances and the configuration required to perform an application, service, processing, or platform function.

Containerized-workload deployment may use:

One or more Container ImagesWorkload configurationRuntime parametersIdentity and access configurationNetwork configurationStorage configurationResource requirementsSecurity controlsService-discovery configurationScaling configurationThe applicable deployment specification determines which inputs apply.

Containerized-workload deployment contributes to:

Repeatable workload creationConsistent runtime configurationAutomated application and service deploymentWorkload portabilityReproducibilityProvenanceTraceability

Applies To

This requirement applies to:

Containerized workloadsContainer ImagesContainer instancesContainer platformsContainer runtimesKubernetes ClustersWorkload configurationWorkload deployment workflowsInfrastructure EnvironmentsProvider ImplementationsCI/CD Pipelines

Verification

Verification SHALL confirm that Crucible executes a deployment operation for a containerized workloadVerification SHALL confirm that the deployment operation targets an identified container platformVerification SHALL confirm that the containerized workload exists on the target container platform after successful deploymentVerification may include:

Containerized-workload deployment testingContainer-platform inspectionContainer-runtime inspectionWorkload-state inspectionDeployment-output inspectionDeployment-log inspectionAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The deployed containerized workloadThe target container platformThe deployment operationThe deployment resultThe observed workload stateThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-DEP-004.

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 a Phase 1 workflow that builds controlled Container Images and deploys platform and application components through an automated CI/CD Pipeline.

FR-DEP-004 establishes the required behavior for deploying a containerized workload to a target container platform.

Requirements governing Container Image building, Kubernetes Cluster deployment, platform services, rollback, and validation define separate behavior.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible deploys a containerized workload to a target container platform.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

This requirement page should retain the stable requirement identifier FR-DEP-004.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

The Statement should remain limited to deployment of a containerized workload.

Requirements for Container Image building, Image Promotion, scaling, availability, rollback, validation, and workload retirement should remain in their applicable requirement pages.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.