Record what v0.17 shipped - #87
Merged
Merged
Conversation
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 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One row in the Shipped table, so the commit the tag lands on contains its own entry.
migrate-seal.shplustests/seal-migration(23 assertions)rotate-keys.sh --unseal-keys, andtests/key-rotationfrom 28 to 46 assertionsBoth needed a prerequisite nobody had noticed:
vault-unsealis the root of trust for the local profile, and the bootstrap held its unseal key in a shell variable and never wrote it down. A singledocker compose restart vault-unsealwas therefore unrecoverable — it came back sealed with nobody holding the key, and cluster nodes restarted afterwards failed to start rather than coming back sealed.That is the same shape as the recovery keys fixed in v0.15, in the place where it costs most.
Tag follows on the merge commit.
🤖 Generated with Claude Code