FR-DEP-003 — Deploy Kubernetes Clusters

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL deploy a Kubernetes Cluster to a target Infrastructure Environment.

Source Statement

The system shall deploy Kubernetes clusters.

Source

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

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 conventionKubernetes Clusters identifies the deployment subject but does not identify the target Infrastructure EnvironmentThe source statement does not prescribe a Kubernetes distribution, topology, provider, installation mechanism, version, or implementation methodThe source statement does not independently require cluster validation, workload deployment, rollback, or compliance assessmentThe normalized Statement:

Replaces The system with CrucibleRetains the direct and testable verb deployIdentifies a Kubernetes Cluster as the deployment subjectIdentifies the target Infrastructure EnvironmentPreserves implementation independenceRetains one primary required behaviorKubernetes Cluster should receive a glossary definition because the term identifies a distinct deployable platform subject used by multiple requirements.

Rationale

A Kubernetes Cluster provides the control plane and worker nodes that schedule, execute, connect, and manage containerized workloads.

A Kubernetes Cluster deployment may include:

Control-plane componentsWorker nodesCluster networkingCluster storage integrationIdentity and access configurationSecurity configurationService discoveryAdmission controlsMonitoring integrationLogging integrationThe applicable Infrastructure Configuration determines which components and values apply to a particular deployment.

Kubernetes Cluster deployment contributes to:

Repeatable container-platform establishmentConsistent cluster configurationAutomated platform creationPortable workload hostingReproducibilityProvenanceTraceability

Applies To

This requirement applies to:

Kubernetes ClustersKubernetes control-plane componentsKubernetes worker nodesCluster networkingCluster storage integrationCluster identity and access configurationCluster security configurationInfrastructure EnvironmentsInfrastructure ConfigurationsKubernetes deployment workflowsProvider ImplementationsCI/CD Pipelines

Verification

Verification SHALL confirm that Crucible executes a deployment operation for a Kubernetes ClusterVerification SHALL confirm that the deployment operation targets an identified Infrastructure EnvironmentVerification SHALL confirm that the Kubernetes Cluster exists in the target Infrastructure Environment after successful deploymentVerification may include:

Kubernetes Cluster deployment testingKubernetes interface inspectionCluster-component inspectionTarget-environment inspectionDeployment-output inspectionDeployment-log inspectionAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The deployed Kubernetes ClusterThe target Infrastructure EnvironmentThe deployment operationThe deployment resultThe observed cluster 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-003.

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

Implementation Status

Not Assessed

Implementation status requires verification that Crucible deploys a Kubernetes Cluster to a target Infrastructure Environment.

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-003.

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 Kubernetes Cluster.

Requirements for containerized workload deployment, platform services, rollback, validation, and cluster 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-003#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.