From d891f993edb384c79251e34cb0bf2a1c2f357c56 Mon Sep 17 00:00:00 2001 From: codex Date: Fri, 19 Jun 2026 17:53:25 -0300 Subject: [PATCH] docs: note soteria bring-up dependencies --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 12f0f1a..7b9bab3 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,22 @@ Policies are stored in a Kubernetes secret and evaluated on a timer. Metrics are The following are notes for future Brad. +## Bring-up dependencies + +Soteria is not how Atlas gets storage back. It is useful after Kubernetes and Longhorn are already alive enough to answer API calls. + +It needs: + +- Kubernetes API, service DNS, and Soteria's service account/RBAC +- Longhorn managers/backend service reachable at `SOTERIA_LONGHORN_URL` +- Longhorn backup target already configured and reachable if backups/restores are expected to work +- the `soteria` namespace and the Kubernetes secret used for backup policies +- ingress/proxy/auth headers if the UI is exposed with auth enabled +- B2 credentials and bucket access only if B2 usage reporting is enabled +- Prometheus/Grafana only for visibility; the service can run without dashboards + +In a total bring-up, fix nodes, disks, Longhorn, and Flux first. Start using Soteria once PVC inventory is visible and Longhorn can make backups without being nursed. + Main endpoints: - `GET /healthz`, `GET /readyz`, `GET /metrics`