Honest first-pass maturity vector grounded in README/docs/tests present in this repo; no invented evidence. Flagged for human review before publish. See reuse-surface history/2026-07-06-coverage-classification.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
122 lines
4.2 KiB
Markdown
122 lines
4.2 KiB
Markdown
---
|
|
id: capability.railiance.cluster-bootstrap
|
|
name: Railiance Cluster Runtime Bootstrap
|
|
summary: 'Cluster runtime entry point of the Railiance Infrastructure-as-Code framework: from two bare
|
|
Linux servers, a Git repo, and credentials, rebuilds a fully automated Kubernetes-based environment.'
|
|
owner: railiance-cluster
|
|
status: draft
|
|
domain: financials
|
|
tags:
|
|
- railiance
|
|
- kubernetes
|
|
- iac
|
|
- bootstrap
|
|
maturity:
|
|
discovery:
|
|
current: D3
|
|
target: D4
|
|
confidence: medium
|
|
rationale: README documents the 'Rails for Ops' convention-over-configuration philosophy and a concrete
|
|
quick-start (clone, from two bare servers rebuild a full k8s environment); has .forgejo CI already
|
|
in place.
|
|
availability:
|
|
current: A2
|
|
target: A3
|
|
confidence: medium
|
|
rationale: Real Python package (pyproject, requires-python >=3.11) plus bin/railiance CLI and ansible
|
|
playbooks (bootstrap/harden), with a documented quick-start path.
|
|
external_evidence:
|
|
completeness:
|
|
level: C1
|
|
confidence: low
|
|
basis: scope_vs_intent_and_consumer_expectations
|
|
satisfied_expectations:
|
|
- documented quick-start from two bare servers to a running Kubernetes environment
|
|
- bootstrap/harden ansible playbooks
|
|
broken_expectations: []
|
|
out_of_scope_expectations: []
|
|
reliability:
|
|
level: R0
|
|
confidence: low
|
|
basis: consumer_quality_signals
|
|
known_reliability_risks:
|
|
- reproducibility claims not independently re-verified (no live bootstrap run during this sweep)
|
|
discovery:
|
|
intent: 'Provide the cluster runtime entry point for Railiance: reproducible, self-reliant Kubernetes
|
|
environment bootstrap from bare servers via convention-over-configuration IaC.'
|
|
includes:
|
|
- cluster bootstrap CLI and ansible playbooks (bootstrap/harden)
|
|
- Kubernetes-based environment rebuild path
|
|
excludes:
|
|
- application workload deployment (see railiance-apps)
|
|
- platform services like Postgres/Valkey (see railiance-platform)
|
|
assumptions: []
|
|
use_cases: []
|
|
research_memos: []
|
|
availability:
|
|
current_level: A2
|
|
target_level: A3
|
|
current_artifacts:
|
|
- '`railiance` CLI (bin/railiance)'
|
|
- ansible playbooks
|
|
target_artifacts: []
|
|
consumption_modes:
|
|
- cli
|
|
- ansible playbook
|
|
relations:
|
|
depends_on: []
|
|
supports: []
|
|
related_to: []
|
|
evidence:
|
|
documentation:
|
|
- README.md
|
|
tests:
|
|
- tests/
|
|
- .forgejo/
|
|
consumer_feedback: []
|
|
bug_reports: []
|
|
incidents: []
|
|
consumer_guidance:
|
|
recommended_for:
|
|
- operators bootstrapping a new Railiance Kubernetes cluster from bare servers
|
|
not_recommended_for:
|
|
- application-level or platform-service deployment (see railiance-apps, railiance-platform)
|
|
known_limitations:
|
|
- reproducibility not independently re-verified via a live bootstrap run in this sweep
|
|
promotion_history: []
|
|
---
|
|
|
|
# Railiance Cluster Runtime Bootstrap
|
|
|
|
## Overview
|
|
|
|
`railiance-cluster` is the cluster runtime entry point of the Railiance Infrastructure-as-Code framework: from two bare Linux servers, a Git repo, and credentials, it rebuilds a fully automated Kubernetes-based environment via convention-over-configuration IaC (Terraform/cloud-init/Ansible-adjacent tooling, `railiance` CLI).
|
|
|
|
## Assessment notes
|
|
|
|
### Discovery
|
|
|
|
README documents the 'Rails for Ops' convention-over-configuration philosophy and a concrete quick-start (clone, from two bare servers rebuild a full k8s environment); has .forgejo CI already in place.
|
|
|
|
### Availability
|
|
|
|
Real Python package (pyproject, requires-python >=3.11) plus bin/railiance CLI and ansible playbooks (bootstrap/harden), with a documented quick-start path.
|
|
|
|
### Completeness
|
|
|
|
First-pass honest assessment from the REUSE-WP-0017 coverage campaign
|
|
(reuse-surface). No external consumer feedback exists yet; levels reflect
|
|
scope-vs-intent documentation quality, not internal code quality.
|
|
|
|
### Reliability
|
|
|
|
No production consumer telemetry exists yet; reliability level is
|
|
intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
|
|
|
|
## Promotion checklist
|
|
|
|
- [x] ID follows `capability.<domain>.<name>` pattern
|
|
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
|
|
- [x] `external_evidence` is populated separately from `maturity`
|
|
- [ ] Relations reference valid capability IDs (none yet)
|
|
- [x] Index entry added in `registry/indexes/capabilities.yaml`
|