coulomb/railiance-cluster
2
0
Fork 0
Code Issues Pull Requests Actions 2 Projects Releases Wiki Activity

chore(workplan): update WP-0002 references after repo rename

Browse Source 
- railiance-hosts → railiance-infra throughout
- ADR-002 → ADR-003 boundary reference
- Remove 'railiance-apps decision pending' note (resolved)

Tasks T01–T05 unchanged — all still todo.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-03-10 00:52:07 +01:00
parent 4561aa5aec
commit 5891f1a881
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ansible/bootstrap.yml
View File

@@ -1,7 +1,7 @@
---
# Pre-condition: the target host must already be converged by railiance-hosts
# Pre-condition: the target host must already be converged by railiance-infra
# (`make converge` in that repo) before running this playbook.
# OS hardening (SSH, UFW, fail2ban) is owned by railiance-hosts — see ADR-002.
# OS hardening (SSH, UFW, fail2ban) is owned by railiance-infra — see ADR-003.
# Install base packages and k3s.
- name: Railiance host bootstrap

20
workplans/RAIL-BS-WP-0002-k3s-baseline.md
View File

@@ -10,7 +10,7 @@ topic_slug: railiance
repo_goal_id: "70ab2379-fb9d-4fec-a09d-b2a717e4ace8"
state_hub_workstream_id: "4c63dfc6-9eac-4e79-9f77-8f644ad7147d"
created: "2026-03-09"
updated: "2026-03-09"
updated: "2026-03-10"
---
# k3s and Kubernetes Platform Baseline
@@ -23,11 +23,11 @@ leaves off: a hardened, verified OS node that is ready for Kubernetes.
## Pre-condition
`railiance-hosts` converge + Goss verify must pass before any task here
`railiance-infra` converge + Goss verify must pass before any task here
is executed:
```bash
# In railiance-hosts/
# In railiance-infra/
make converge
make verify # must exit 0
```
@@ -35,12 +35,12 @@ make verify # must exit 0
## Boundary
This repo owns everything from k3s upward. It must not re-configure items
defined in `railiance-hosts/spec/server-baseline.yaml`. See
`railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md`.
defined in `railiance-infra/spec/server-baseline.yaml`. See ADR-003:
`railiance-infra/docs/adr/ADR-003-railiance-5repo-stack-architecture.md`.
**Out of scope here:** application-layer deployments (Gitea, monitoring
stack, user-facing services). Those belong in `railiance-apps` once that
repo is established (decision pending).
**Out of scope here:** platform services (PostgreSQL, storage, identity)
→ `railiance-platform`. Application deployments (Gitea, coulomb services)
→ `railiance-apps`.
---
@@ -164,6 +164,6 @@ smoke: ## Run Kubernetes smoke tests
- Repo goal: `70ab2379-fb9d-4fec-a09d-b2a717e4ace8` (Install k3s and Kubernetes Baseline)
- Domain goal: `6f96c712-60e6-4ea9-ab06-168878eafbce` (Three-Phoenix Secure Kubernetes Infrastructure)
- Pre-condition: railiance-hosts WP-0001 (Secure Single-Server Bootstrap) — completed 2026-03-09
- Boundary ADR: `railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md`
- Pre-condition: railiance-infra WP-0001 (Secure Single-Server Bootstrap) — completed 2026-03-09
- Boundary ADR: `railiance-infra/docs/adr/ADR-003-railiance-5repo-stack-architecture.md`
- k3s releases: https://github.com/k3s-io/k3s/releases