Repository navigation
Conversation
One-off build (0.6.5-mrgk) for joining two independently bootstrapped off-chain KMS clusters, not for regular releases. Onboard takes merge_source_url/merge_source_token: the source's whole keyring is imported as usual, and the single root of the merge source is appended as the next epoch instead of a generated one. The merge source is pinned to the root CA it publishes, once its public keys extend the imported keyring to the latest registered chain hash, and is authorized by the auth API like the source. The merged keyring is then checked as an ordinary join with the new epoch pending activation. Signed-off-by: Kevin Wang <wy721@qq.com>
kvinwang
marked this pull request as draft
November 17, 2026 03:05
The merged keyring is checked against the registered chain hash before use, and the merge source releases its keys only to an attested KMS its own auth API allows, so pinning it through its published GetMeta keys only guarded the admin token. Signed-off-by: Kevin Wang <wy721@qq.com>
This branch has not been deployed
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
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-off build for joining two independently bootstrapped off-chain KMS clusters into one keyring. Not to be merged into
nextor any regular release;kms-v0.6.5-mrgkis tagged from this branch. The PR is for review and the public record.Onboardtakesmerge_source_url/merge_source_token. The source's keyring is imported as usual, and the merge source's single root is appended as the next epoch instead of a generated one:Derived keys do not depend on the root epoch number, so the merge source's apps keep their keys once the epoch is activated. Procedure:
docs/kms-root-merge.md.E2E on real TDX (two 0.6.3 KMS clusters with dstack-auth webhooks -> merge -> official 0.6.5 join -> activation): all 22 steps pass. Before activation the merged cluster serves the old root; after activation the merge sources app on an unchanged 0.6.3 guest keeps byte-identical derived keys, and the old clusters app migrates disk and env on a 0.6.5 guest.