feat(fleet): provision subordinate nodes from the adopt flow - #60
Merged
Conversation
The adopt handler hardcoded the root first-boot ceremony, so only self-signed root nodes could be provisioned. Select the ceremony by role: a root self-signs via FIRST_BOOT_ROOT as before; an intermediate/issuing node skips the ceremony (the node stages its own subordinate CSR on boot) and completes adoption in an awaiting-certificate state, registered and ready for a parent-signed chain. The chain is delivered by the existing SUBORDINATE enrollment ferry (child CSR -> parent SignSubordinateCSR -> child SubmitSubordinateCertificate), which brings the node to established under its parent. Closes #59
Bugs5382
force-pushed
the
fix/59-adopt-subordinate
branch
from
July 25, 2026 17:55
41fefbd to
cb3d044
Compare
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.
What
Selects the first-boot ceremony by node role so the adopt flow can stand up subordinates, not just roots:
FIRST_BOOT_ROOT(unchanged).awaiting-certificatestate, registered with its managed admin credentials.The parent-signed chain is then delivered by the existing SUBORDINATE enrollment ferry (child
GetSubordinateCSR→ parentSignSubordinateCSR→ childSubmitSubordinateCertificate), bringing the node to established under its parent.Why
Full web parity means an operator can stand up a two-tier CA (root + intermediate) without the CLI. Proven live on ESXi: adopted cryptos-lab-b as an intermediate (terminal
awaiting-certificate), then a SUBORDINATE enrollment established it as "CryptOS Lab Intermediate CA" issued by "CryptOS Lab Root CA"; a subsequent subordinate rekey succeeded.Closes #59
Part of #24