railiance-infra/docs/convergence.md
codex e176738fad
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Define S1 reef rollout handoff
2026-07-25 15:13:41 +02:00

1.6 KiB

🔧 Server Convergence

After provisioning servers with Terraform, railiance-infra uses Ansible to bring them into a secure and usable baseline state.
This process is called convergence.

What Convergence Does

When you run make converge, Ansible connects to all declared hosts and applies baseline roles:

  • User setup → ensures the admin user exists with your SSH key and passwordless sudo
  • Firewall → configures ufw with sensible defaults (deny incoming, allow SSH)
  • Hardening → basic SSH daemon hardening, disable root login, disable password auth
  • Tooling → installs essential packages (htop, vim, git, curl, fail2ban, etc.)
  • SOPS agent → ensures decryption tooling (age, sops) is available on the host

Running Convergence

make converge

This will:

  1. Decrypt secrets locally (with your age key)
  2. Run the Ansible playbooks against all hosts in your inventory/servers.yaml
  3. Apply the baseline security and tooling configuration

Verifying

After convergence, run the automated test suite to assert the node matches the baseline spec:

make verify

This runs Goss assertions against all hosts and exits non-zero on failure. TAP reports are written to reports/. See docs/verification.md for details.

For a quick human-readable summary without assertions:

make status

Notes

  • Convergence is idempotent: re-running it will not break your server.
  • Only your workstation (control node) needs the age private key; hosts never see it.
  • Additional roles (e.g. WireGuard, Kubernetes, apps) can be layered later.