From f383996127536216eaf4bec6b407727338a809d6 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Thu, 8 Oct 2026 08:13:18 -0400 Subject: [PATCH] docs: soften shared-volume remark in secrets runbook (#623) Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe --- docs/operations/2026-07-16-secrets-clustered-master-key.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/operations/2026-07-16-secrets-clustered-master-key.md b/docs/operations/2026-07-16-secrets-clustered-master-key.md index c62343d0..df2347f8 100644 --- a/docs/operations/2026-07-16-secrets-clustered-master-key.md +++ b/docs/operations/2026-07-16-secrets-clustered-master-key.md @@ -113,8 +113,7 @@ fleet-wide order. The earlier interim posture — every node of a pair mounting one `Secrets:SqlitePath` on a shared or replicated volume — still works for a deployment that keeps `Secrets:Replication:Enabled=false`: reads dominate and writes are effectively single-writer. See the caveat below; it is not safe with -concurrent writers, and it is not available to DB-less driver-only site nodes that have no shared -volume with their partner. +concurrent writers, and it is impractical for site pairs whose nodes share no volume. ## How it's delivered (do NOT commit these values)