From 0f13066275adda8414de6ebeacd4979bf5c01152 Mon Sep 17 00:00:00 2001 From: bstein Date: Fri, 19 Jun 2026 21:27:06 +0000 Subject: [PATCH] Update README.md --- README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 23121a0..985e046 100644 --- a/README.md +++ b/README.md @@ -14,9 +14,7 @@ The following are notes for future Brad. ## Bring-up dependencies -Ariadne is not first-wave recovery software. Bring it up after the cluster can already run normal in-cluster services. - -It needs: +Ariadne needs: - Kubernetes API, service DNS, and Ariadne's service account/RBAC - the Ariadne database, plus the portal database if portal/account sync is enabled @@ -25,7 +23,7 @@ It needs: - ingress/proxy plumbing if humans are going to use it through the portal - the services for whatever jobs are enabled: Mailu, Nextcloud, Vaultwarden, Wger, Firefly, Jenkins, Metis, OpenSearch, and the comms/game-mode pieces -It can start before every integration is perfect, but the matching scheduled jobs will fail or no-op until their service is actually alive. In a total bring-up, wait for storage, Flux, Postgres, Vault, Keycloak, and ingress first; then Ariadne becomes useful glue. +It can start before every integration is perfect, but the matching scheduled jobs will fail or no-op until their service is actually alive. In a total bring-up, wait for storage, Flux, Postgres, Vault, Keycloak, and ingress first. Afterwards Ariadne becomes useful glue. Useful routes: