FR-DEP-003 — Deploy Kubernetes Clusters

Go to Crucible Deployment Orchestration Requirements

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

The system shall deploy Kubernetes clusters.

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

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 name
• 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 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.

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 components
• 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.

Kubernetes Cluster deployment contributes to:

• Repeatable container-platform establishment
• Consistent cluster configuration
• Automated platform creation
• Portable workload hosting
• Reproducibility
• Provenance
• Traceability

This requirement applies to:

• Crucible
• Kubernetes Clusters
• Kubernetes control-plane components
• Kubernetes worker nodes
• Cluster networking
• Cluster storage integration
• Cluster identity and access configuration
• Cluster security configuration
• Infrastructure Environments
• Infrastructure Configurations
• Kubernetes deployment workflows
• Provider Implementations
• CI/CD Pipelines

1. Verification SHALL confirm that Crucible executes a deployment operation for a Kubernetes Cluster
2. Verification SHALL confirm that the deployment operation targets an identified Infrastructure Environment
3. Verification SHALL confirm that the Kubernetes Cluster exists in the target Infrastructure Environment after successful deployment

Verification may include:

• Kubernetes Cluster deployment testing
• Kubernetes interface inspection
• Cluster-component inspection
• Target-environment inspection
• Deployment-output inspection
• Deployment-log inspection
• Automated CI/CD Pipeline testing

The verification record SHALL identify:

1. The deployed Kubernetes Cluster
2. The target Infrastructure Environment
3. The deployment operation
4. The deployment result
5. The observed cluster state
6. The generated Evidence

This requirement realizes:

• MO-001
• MO-002
• MO-003
• MO-006

This requirement relates to:

• FR-DEP-001 — Deploy Infrastructure Resources
• FR-DEP-004 — Deploy Containerized Workloads
• FR-DEP-005 — Deploy Platform Services
• FR-DEP-006 — Deployment Rollback
• FR-DEP-007 — Deployment Validation
• 7. Infrastructure and Deployment

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.

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.

Phase 1

Not Assessed

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

Draft

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

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.