afterburn: set ssh keys for hetzner OEM #118
Merged
Conversation
This file contains 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
This was referenced Apr 11, 2024
tormath1
reviewed
Apr 16, 2024
tormath1
approved these changes
Apr 16, 2024
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.
Use SSH Keys from metadata service for Hetzner OEM
Enables the existing afterburn service for the
hetznerOEM. This will read the SSH Key(s) that the user configured for the server from the metadata service, and add them to thecoreuser.How to use
Changes are pulled into
flatcar/scriptsin flatcar/scripts#1880. This also explains how to use/test them.Testing done
I have referenced this commit in
flatcar/scriptsoverlay and built a test image. A server created from this image did correctly read and configure the SSH Key. I was able to login and the file/home/core/.ssh/authorized_keyscontained my key.changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.RE the above checkboxes, I was not sure if I should add a changelog, some other recent PRs for Proxmox and Akamai did not add any changelog entries.