Files
railiance-cluster/ansible/harden.yml
tegwick 783c8cebbd feat(boundary): remove OS-hardening overlap; add k3s baseline workplan
Per ADR-002 (railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md):
- ansible/harden.yml: replaced with tombstone pointing to railiance-hosts
- ansible/bootstrap.yml: remove `import_playbook: harden.yml`; add
  pre-condition comment; OS hardening is no longer this repo's concern
- docs/first_host.md: rewritten to reflect 3-step flow:
  converge railiance-hosts → railiance-bootstrap k3s install → smoke test
- workplans/RAIL-BS-WP-0002-k3s-baseline.md: new workplan for k3s +
  Helm + Kubernetes platform baseline; linked to repo goal 70ab2379

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-09 19:53:22 +01:00

17 lines
655 B
YAML

---
# SUPERSEDED — do not use for new work.
#
# OS security hardening (SSH, UFW, fail2ban, HISTCONTROL) is now owned by
# the railiance-hosts repository:
#
# railiance-hosts/ansible/roles/base/
# railiance-hosts/spec/server-baseline.yaml ← authoritative spec
# railiance-hosts/goss/baseline.yaml ← automated assertions
#
# Run `make converge` in railiance-hosts before deploying anything from
# this repo. See ADR-002 for the full boundary definition:
# railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md
#
# This file is retained to avoid breaking git history references.
# It must not be imported or executed.