railiance-cluster/registry/capabilities/capability.railiance.cluster-bootstrap.md
codex 750c3e5b9b
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:41:51 +02:00

116 lines
3.7 KiB
Markdown

---
id: capability.railiance.cluster-bootstrap
name: Kubernetes runtime and cluster controls
summary: k3s, ingress, CNI, operators and kubeconfig/runtime checks.
owner: railiance-cluster
status: draft
domain: financials
tags:
- railiance
- kubernetes
- iac
- bootstrap
- security
- netkingdom
- framework-reuse
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: 'Source interface assessed 2026-10-14: k3s, ingress, CNI, operators
and kubeconfig/runtime checks. Availability describes the delivery form, not
production acceptance. Single-node runtime and workload recovery are distinct
from bootstrap success.'
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: k3s, ingress, CNI, operators and kubeconfig/runtime checks
includes:
- k3s, ingress, CNI, operators and kubeconfig/runtime checks
excludes:
- Single-node runtime and workload recovery are distinct from bootstrap success
assumptions: []
use_cases:
- 'U10: Operator recovers identity, custody or data with independently held recovery
material'
- 'U13: Platform owner deploys and rolls back a workload with explicit substrate
and custody bindings'
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- SCOPE.md
target_artifacts: []
consumption_modes:
- CLI
- source
relations:
depends_on: []
supports: []
related_to:
- capability.security.iam-tooling-suite
evidence:
documentation:
- SCOPE.md
tests:
- tests/
- .forgejo/
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- Operator recovers identity, custody or data with independently held recovery material
- Platform owner deploys and rolls back a workload with explicit substrate and custody
bindings
not_recommended_for:
- Single-node runtime and workload recovery are distinct from bootstrap success
known_limitations:
- Single-node runtime and workload recovery are distinct from bootstrap success
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
promotion_history: []
---
# Kubernetes runtime and cluster controls
k3s, ingress, CNI, operators and kubeconfig/runtime checks.
## Reuse boundary
Single-node runtime and workload recovery are distinct from bootstrap success.
## Supported use cases
- U10: Operator recovers identity, custody or data with independently held recovery material
- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings
## Evidence and integration
- [SCOPE.md](../../SCOPE.md)
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.