From 0ed4c05ac221c0613d0df38269c73e57e6a056f7 Mon Sep 17 00:00:00 2001 From: Seth Bergman Date: Tue, 8 Sep 2026 16:33:57 -0500 Subject: [PATCH] Record what v0.17 shipped Seal migration in both directions, the unseal-key rekey, and the fix underneath both: vault-unseal is the root of trust for the local profile and the bootstrap was discarding its unseal key, so a restart of that one container ended the cluster. The tag goes on the commit after this one, so the tagged tree contains its own entry. Co-Authored-By: Claude Opus 5 --- docs/roadmap.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/roadmap.md b/docs/roadmap.md index 392803b..3974d8f 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -26,6 +26,7 @@ and which parts are a plausible-looking configuration nobody has run. | v0.14 | Five cloud defects found and fixed without an apply: static pre-flight, and a real apply against an emulated AWS API | | v0.15 | Remote, locked Terraform state; the autopilot default that walks an instance refresh out of quorum; quorum recovery and the root token, both closed without a cloud account | | v0.16 | Audit anchors shipped to storage that refuses to delete them, on both clouds; key rotation and recovery rekey; a snapshot read back out of object storage and restored | +| v0.17 | Seal migration in both directions, and the unseal-key rekey — plus the key the local root of trust had been discarding, which made restarting one container unrecoverable | ## The honest gap