Railiance S2 cluster runtime layer for Kubernetes installation, networking, ingress, operators, and verified cluster health.
Find a file
tegwick 0814ed3a19
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Repurpose as the Railiance bootstrap path
This repo carried a copied declaration identifying it as the S2 cluster runtime
layer - byte-similar to railiance-cluster, with which it shares no git history
but nearly all of its content. It was one of four repos (bootstrap, cluster,
hosts, infra) created by copying working trees as the S1/S2 layering idea
emerged, and the INTENT was copied along with everything else.

Its own QUICKSTART.md - set up your very first Railiance host - describes what
the repo is actually for. INTENT.md and SCOPE.md now declare that: turning a
single bare virtual machine into a working Railiance, then handing off to the
ordinary layers.

Inherited S2-era content in ansible/, helm/, docs/ and wiki/ is not yet sorted;
SCOPE records that restructuring is in progress rather than claiming it is done.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 22:41:29 +02:00
.claude/rules docs: workplan-first agent guidance prose (CUST-WP-0055 T04 batch 3) 2026-07-08 17:15:39 +02:00
.forgejo/workflows Add Forgejo CI smoke workflow (enablement template) 2026-07-04 12:50:02 +02:00
.github/workflows railiance: initial bootstrap scaffold 2025-09-12 01:46:14 +02:00
ansible fix(bootstrap): commit full bootstrap.yml — Helm + kubeconfig tasks 2026-03-10 09:52:36 +00:00
bin RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling 2026-07-02 10:44:06 +02:00
cloudinit chore(relocate): stub out S1 items moved to railiance-infra 2026-03-10 00:35:04 +01:00
docs RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling 2026-07-02 10:44:06 +02:00
examples/railiance Define Railiance app contract 2026-06-27 15:33:47 +02:00
helm feat(boundary): move Gitea Helm values to railiance-apps (T06) 2026-03-27 13:23:41 +01:00
lib refactor: separated command script 2025-09-13 02:39:47 +02:00
registry Add capability registry scaffold (REUSE-WP-0014-T07 B05) 2026-06-16 01:57:57 +02:00
schemas Define Railiance app contract 2026-06-27 15:33:47 +02:00
tests fix(test): correct ha-failover test — wrong URL, wrong pod label, missing kubectl 2026-03-10 13:42:54 +00:00
tools RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling 2026-07-02 10:44:06 +02:00
wiki docs: add ThreePhoenix architecture concept and workplan 2026-02-25 01:13:05 +01:00
workplans CUST-WP-0055 T07: add archive workplan terminology grandfather note 2026-07-08 20:26:36 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-02 11:53:28 +02:00
.editorconfig chore: optimize .editorconfig for consistent coding style 2025-09-12 02:19:01 +02:00
.gitattributes chore: .gitattributes updated for line ending normalization 2025-09-12 02:21:05 +02:00
.gitignore feat(secrets): encrypt gitea Helm values with SOPS (age) 2026-03-10 13:37:22 +00:00
.repo-classification.yaml Add .repo-classification.yaml (CUST-WP-0050 T11 agent first-pass) 2026-06-22 17:47:40 +02:00
.sops.yaml feat(secrets): encrypt gitea Helm values with SOPS (age) 2026-03-10 13:37:22 +00:00
AGENTS.md Regenerate agent instructions from state-hub templates (CUST-WP-0055 T01) 2026-07-08 14:50:33 +02:00
CLAUDE.md Regenerate agent instructions from state-hub templates (CUST-WP-0055 T01) 2026-07-08 14:50:33 +02:00
DECISIONS.md feat(backup): revise WP-0004 — integrated backup per capability (D4) 2026-03-10 17:43:30 +01:00
INTENT.md Repurpose as the Railiance bootstrap path 2026-08-11 22:41:29 +02:00
LICENSE chore: add MIT License 2025-09-12 02:44:03 +02:00
Makefile RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling 2026-07-02 10:44:06 +02:00
pyproject.toml chore(rename): railiance-bootstrap → railiance-cluster 2026-03-10 00:34:21 +01:00
QUICKSTART.md chore(rename): railiance-bootstrap → railiance-cluster 2026-03-10 00:34:21 +01:00
README.md tools and workplans 2026-05-15 23:03:28 +02:00
sbom-tools.yaml chore(sbom): add system-level tool dependency manifest 2026-03-18 18:31:12 +01:00
SCOPE.md Repurpose as the Railiance bootstrap path 2026-08-11 22:41:29 +02:00
uv.lock tools and workplans 2026-05-15 23:03:28 +02:00

Railiance Cluster

License: MIT

Opinionated Infrastructure-as-Code framework for reproducible, self-reliant systems.

Railiance is an opinionated Infrastructure-as-Code framework
think Rails for Ops: convention over configuration, reproducibility first.

This repo (railiance-cluster) is the cluster runtime entry point:
from two bare Linux servers, a Git repo, and credentials, you can rebuild
a fully automated Kubernetes-based environment.


🚀 Quick Start

  1. Clone this repo

    git clone <your-gitea-url>/railiance-cluster.git
    cd railiance-cluster
    
  2. Configure Gitea access
    Edit ~/.railiance_gitea.conf with your server URL, username, and token.
    (Never commit this file!)

  3. Bootstrap a host
    Run the Ansible playbooks in ansible/ to set up k3s, Helm, kubectl.

  4. Deploy baseline services
    Use helm/ charts to roll out essential services (GitOps, monitoring, etc.).

  5. Validate
    Check the automated tests in tests/ to confirm infra health.


📂 Repo Structure

  • ansible/ — Playbooks for provisioning
  • helm/ — Opinionated Helm charts
  • k8s/ — Kubernetes manifests
  • tests/ — Automated validation
  • docs/ — Documentation (see docs/README.md)
  • tools/ — Helper scripts (e.g. create_railiance_repo.sh)

🤝 Contributing

See docs/CONTRIBUTING.md.


🌍 Vision

Railiance aims for self-reliant infrastructure:
automation you can rebuild from scratch, with calmness and clarity.

From bare metal to resilient clusters — in one repo.