From bb86ce2dae350bb0fc44ccd5498e1ea960d026b8 Mon Sep 17 00:00:00 2001 From: bstein Date: Fri, 19 Jun 2026 21:00:55 +0000 Subject: [PATCH] Update README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 88c8cb7..b9ed336 100644 --- a/README.md +++ b/README.md @@ -22,12 +22,12 @@ The following are notes for future Brad. ## Bring-up dependencies -Ananke should be one of the first things working. It does not need Harbor, Gitea, Longhorn, Grafana, or the apps to be healthy before it starts; those are often the mess it is there to sort out. +Ananke should be one of the first things working. It does not need Harbor, Gitea, Longhorn, Grafana, or the apps to be healthy before it starts; their mess is what Ananke was born to sort out. -It does need: +Ananke needs: -- an Ananke host that came up on its own: usually `titan-db`, with the `tethys`/`titan-24` peer path as the backup -- `/etc/ananke/ananke.yaml`, the Ananke SSH key, and enough host config to reach nodes on the Atlas SSH port +- an Ananke host that came up on its own: usually `titan-db` (for the arm64 ups) and `tethys`/`titan-24` (for amd64 ups) +- `/etc/ananke/ananke.yaml`, the Ananke SSH key, and enough host ssh config to reach nodes on the Atlas SSH port - Kubernetes API access once the control plane is answering; before that it can only do host-side checks - Flux CRDs/controllers and the `titan-iac` source once the API is up, because most startup gates are Flux-shaped - basic node hygiene that Ananke cannot fake forever: SSH, sudo for managed repairs, sane clocks, and Longhorn host packages like `cryptsetup`, `open-iscsi`, `dmsetup`, and `nfs-common`