bstein/ananke
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
bstein 2026-06-19 21:00:55 +00:00
parent 9a741def21
commit bb86ce2dae
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -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`