-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update recipes to support JWT-backed cloud-init #67
Conversation
91220b5
to
50836b6
Compare
d091322
to
36ab066
Compare
This should now be fully documented and ready to merge, and replaces #44 (by virtue of integrating the most recent cloud-init server). However, we may also want to look at the details of #44, particularly |
Note that we do not perform SSH host key checking. Host keys are treated as secrets, and will be applied via cloud-init *after* all TPM operations have completed (since this needs the key that we store into the TPM).
When a node requests its bootscript, BSS can now initiate a POST request to and endpoint of the user's choice — in this case, to the TPM manager daemon. This notification includes the booting node's IP address, which is passed to Ansible as inventory to be configured with a TPM key.
The tpm-manager compose file, in particular, includes an override clause which enables the cloud-init server's "secure route" (i.e. JWT-authenticated config data).
This is, usually, required so that Ansible in the container can SSH to nodes.
36ab066
to
4afa858
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Added
Changed
Related