Document the Vault-free runtime architecture - #5649
Draft
Sinck wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Bill Minckler <wminckler@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
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.
This documents the target architecture for removing the NICo runtime dependency on Vault/OpenBao across credential storage, node API authentication, and the remaining key and certificate services. It keeps the completed subsystem designs authoritative while making the cross-epic dependencies explicit, so transitional states such as Transit-held KEKs and JWTs signed with the mTLS certificate key are not mistaken for the end state.
The design also records the manually installed fTPM certificate lifecycle as an open question and clarifies that a zero
stale_remainingcount covers live database rows only; old KEKs must remain available for retained backups and rollback windows.Related issues
Closes #3251
Type of Change
Breaking Changes
Testing
Additional Notes
Sections 1–7 describe the completed target architecture. Section 8 is a dated implementation snapshot that records intentional intermediate states between the three epics and points to the work that resolves each one. Detailed behavior for completed tasks remains in the linked subsystem design documents.