Documentation / Reference
Reference · v0.0.1 v0.0.1 release status Separate implemented contracts from approved runtime capability and understand the remaining production-readiness boundary.
Audience Buyers, evaluators, change approvers, operatorsReading time 13 minCommands in context 5 guided stepsReviewed source fcc5871 · 30 July 2026
RC Exact release scope. This page documents the reviewed v0.0.1 source at fcc5871. Check release status before enabling a gated capability.
Current statement Release candidate v0.0.1 is not GA-ready. The release branch is merged through fcc5871; exact-head CI and CodeQL are green. Signed customer release publication and environment-specific approval still gate production use.
ClusterPilot has substantial implemented code, tests, operator contracts, and release gates. “Implemented,” “tested locally,” “available behind a gate,” and “production approved” are different states.
Capability maturity Capability Status Customer interpretation Control plane Production-gated Deploy only under the signed release and environment approval. Providers Stable + production-gated Hetzner and IONOS are enabled/supported; AWS and Azure are disabled. Cluster infrastructure/lifecycle Production-gated Enabled on clean installs; production still requires signed release and environment approval. Kubernetes reads Preview Bounded inventory, logs and Helm read paths are enabled. Sensitive Kubernetes mutations Contract-only Do not plan on exec, port-forward, generic mutation, RBAC/Secret administration. Add-on install Production-gated Plan, preflight, install and health evidence are implemented; environment approval remains required. Add-on upgrade/uninstall Stub/disabled Not a current operational capability. Conformance Candidate Pinned Sonobuoy workflow awaiting complete release evidence. Self-hosted/air-gap distribution Production-gated No broad production or full-sovereignty claim.
Open release evidence ✓ Signed customer release publication from the accepted release workflow.
✓ Customer-environment approval for the selected supported provider, network, cluster and operating profile.
✓ Environment-specific create/update/failure/cleanup and quota/rate-limit acceptance.
✓ Real OCI/Harbor, private-CA, digest-promotion, and no-egress installation/operation.
✓ Quick, non-disruptive, and certified Sonobuoy modes on supported cluster baselines.
✓ Control-plane and agent restart, stale lease, failure injection, artifact corruption/purge, cleanup recovery.
✓ Signed candidate promotion and independent release acceptance evidence.
Commands for this step Write and validate the exact release evidence root Release engineering binds development, environment, checksum, and validation evidence to one candidate before approval.
Protected workflow Run only on an approved maintainer, security, or release system.
01
Changes state PowerShell
Write the canonical release evidence manifest Bind workflow identity, runtime images, SBOMs, CVE summaries, provenance, signed packages and rollout status in one release evidence root.
Before you run it All named release artifacts already exist Exact workflow/run/commit identity Approved dev/environment validation result PowerShell · release-evidence-write Copy
& ./scripts/release/write-release-evidence.ps1 `
-EvidenceRoot ./artifacts/release-evidence `
-ReleaseVersion <release-version> `
-CommitSha "<candidate-commit-sha>" `
-WorkflowRunId "<workflow-run-id>" `
-WorkflowRunAttempt "<workflow-run-attempt>" `
-WorkflowName release `
-Repository ClusterPilot-System/clusterpilot `
-SourceRef refs/heads/release/v0.0.1 `
-BuildTimestampUtc <iso-8601-utc> `
-RegistryHost ghcr.io `
-RegistryNamespace <owner> `
-ApiImageRepository <api-image-repository> `
-ApiImageDigest "sha256:<api-digest>" `
-AgentImageRepository <agent-image-repository> `
-AgentImageDigest "sha256:<agent-digest>" `
-ApiSbomPath sbom/clusterpilot-image.cyclonedx.json `
-AgentSbomPath sbom/clusterpilot-agent-image.cyclonedx.json `
-ApiCveSummaryPath cve/grype-summary.json `
-AgentCveSummaryPath cve/grype-agent-summary.json `
-ApiProvenancePath provenance/clusterpilot-api-provenance-registry.bundle.json `
-AgentProvenancePath provenance/clusterpilot-agent-provenance-registry.bundle.json `
-ReleaseBundlePath <release-bundle-path> `
-ReleaseBundleSignaturePath <release-bundle-signature-path> `
-HelmChartPath <helm-chart-path> `
-HelmChartSignaturePath <helm-chart-signature-path> `
-ReleaseManifestPath manifest.json `
-ReleaseManifestSignaturePath signatures/manifest.json.sig `
-DevValidationStatus <passed-or-governed-status> `
-RollbackCommand "<approved-rollback-command>"✓ Expected result The evidence root contains a deterministic manifest linking every release-owned proof.
Reviewed source scripts/release/write-release-evidence.ps102
Changes state PowerShell
Write development validation evidence Record a development dry-run or environment outcome against the exact release candidate.
Before you run it Exact candidate and workflow identity Retained development validation outputs PowerShell · release-dev-evidence-write Copy
& ./scripts/release/write-dev-validation-evidence.ps1 `
-EvidenceRoot ./artifacts/release-evidence `
-ReleaseVersion <release-version> `
-CommitSha "<candidate-commit-sha>" `
-WorkflowRunId "<workflow-run-id>" `
-ValidationMode dry-run-only `
-Status <passed-or-governed-status> `
-DevNamespace clusterpilot-dev `
-HelmReleaseName clusterpilot-dev `
-ApiImageDigest "sha256:<api-digest>" `
-AgentImageDigest "sha256:<agent-digest>" `
-HealthStatus <status> `
-ReadyStatus <status> `
-ApiSmokeStatus <status> `
-FrontendSmokeStatus <status> `
-RollbackCommand "<approved-rollback-command>" `
-Reason "<decision-reason>"✓ Expected result Development acceptance or skip/failure reason is recorded without being promoted to production proof.
Reviewed source scripts/release/write-dev-validation-evidence.ps103
Changes state PowerShell
Write named environment validation evidence Record pre-production or other governed environment validation against the exact release candidate.
Before you run it Named lower-case environment Exact candidate/workflow identity Retained validation and rollback evidence PowerShell · release-environment-evidence-write Copy
& ./scripts/release/write-environment-validation-evidence.ps1 `
-EnvironmentName preprod `
-EvidenceRoot ./artifacts/release-evidence `
-ReleaseVersion <release-version> `
-CommitSha "<candidate-commit-sha>" `
-WorkflowRunId "<workflow-run-id>" `
-ValidationMode <validation-mode> `
-Status <passed-or-governed-status> `
-RuntimeMode <helm-or-compose> `
-HostName <validated-host> `
-InstallRoot <install-root> `
-EnvFilePath <protected-env-path> `
-ComposeProjectName <compose-project> `
-Namespace <namespace> `
-HelmReleaseName <helm-release> `
-ApiImageDigest "sha256:<api-digest>" `
-AgentImageDigest "sha256:<agent-digest>" `
-HealthStatus <status> `
-ReadyStatus <status> `
-ApiSmokeStatus <status> `
-FrontendSmokeStatus <status> `
-RollbackCommand "<approved-rollback-command>" `
-Reason "<decision-reason>"✓ Expected result A secret-safe environment evidence record binds topology, runtime identities, checks and decision reason.
Reviewed source scripts/release/write-environment-validation-evidence.ps104
Changes state PowerShell
Update release evidence manifest checksums Recompute the governed checksum map after all evidence files are final and before signing/publication.
Before you run it Complete final evidence root No concurrent writer PowerShell · release-evidence-checksums Copy
& ./scripts/release/update-release-evidence-manifest-checksums.ps1 `
-EvidenceRoot ./artifacts/release-evidence✓ Expected result The manifest checksum set matches every governed evidence file.
Reviewed source scripts/release/update-release-evidence-manifest-checksums.ps105
Read-only PowerShell
Validate the complete release evidence root Independently reject missing, mismatched or internally inconsistent release evidence before publication.
Before you run it Final evidence root with checksum manifest and referenced artifacts PowerShell · release-evidence-validate Copy
& ./scripts/release/validate-release-evidence.ps1 `
-EvidenceRoot ./artifacts/release-evidence✓ Expected result Every required evidence file, identity and checksum validates.
Reviewed source scripts/release/validate-release-evidence.ps1How to communicate the product Acceptable Not acceptable for v0.0.1 Self-hosted by design; customer operates the environment. Fully sovereign or compliant by installation alone. Deterministic plans, guarded OperationRuns, and evidence contracts are implemented. Autonomous management or guaranteed zero-touch recovery. Supports release-scoped evaluation of multiple provider adapters. Production-ready multi-cloud platform. Signed/digest-pinned distribution and air-gap-oriented contracts exist. Every air-gap topology is validated and supported. No mandatory SaaS control plane. No external dependency or customer operational responsibility.
Environment approval checklist ✓ Required capabilities and provider have named owners and exact gates.
✓ Target profile and dependencies meet availability, security, backup, retention, and support objectives.
✓ Install, upgrade, rollback/restore, agent rollout, lifecycle, add-on, conformance, and delete are rehearsed.
✓ Known limitations are accepted by product, security, operations, and change authority.
✓ Release, environment, evidence, approver, expiration, and rollback are recorded.
