Table of Contents

FR-DEP-003 — Deploy Kubernetes Clusters

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL deploy Kubernetes Clusters.

Derived From

This requirement derives from:

The Original Requirement states:

The system shall deploy Kubernetes clusters.[C1]

FR-DEP-003:

No other substantive normalization is required.

Rationale

A Kubernetes Cluster provides the control-plane and worker-node capabilities required to schedule, execute, connect, and manage containerized workloads.

Deploying Kubernetes Clusters enables Crucible to establish Kubernetes-based platforms through separately governed deployment workflows.

This requirement establishes Kubernetes Cluster deployment without prescribing:

Separate requirements define those subjects and behaviors.

Applies To

This requirement applies to:

Verification

Verification confirms that:

  1. One or more Kubernetes Clusters are selected for deployment
  2. Crucible executes a deployment operation for the selected Kubernetes Clusters
  3. The completed deployment produces the selected Kubernetes Clusters
  4. The resulting Kubernetes Clusters can be identified as outputs of the tested deployment

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Review and approve FR-DEP-003 as a leaf requirement.


Issues

Determine whether separate requirements identify the configuration used for each Kubernetes Cluster deployment.

Determine whether separate requirements identify the Deployment Target or Infrastructure Environment for each Kubernetes Cluster deployment.


Notes for Editors

This requirement page retains the stable requirement identifier FR-DEP-003.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement preserves the approved source intent by requiring Crucible to deploy Kubernetes Clusters.

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:

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

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