-
Notifications
You must be signed in to change notification settings - Fork 25
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
docs(hetzner): update for new OEM images #336
Conversation
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. There are two small comments to address and I think we can add a note regarding the Afterburn issue you found directly under the Butane example.
EDIT: we can squash everything in one commit.
Describe the process to upload the image using Packer or hcloud-upload-image.
Cleaned everything up, fixed the Afterburn issue and squashed it all into a single commit :) |
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.
Many thanks for all your efforts and your contributions regarding Hetzner and Flatcar support. 🙏
Update Hetzner docs for new OEM images, explaining the Snapshot process
Now that the
beta
andalpha
releases include Hetzner OEM images we can update the docs to utilize these images.The current terraform process is okay for a single server, but if you want to create a fleet of servers you want to re-use the snapshots to create new servers quicker.
I was not sure which option is actually easier, Packer or
hcloud-upload-image
, so I documented both for now.In comparison to https://github.com/apricote/flatcar-packer-hcloud/ I tried to remove any bells and whistles from the Packer template, to keep it as short as possible for the docs and easy to understand.
Related to flatcar/Flatcar#1412.
Disclaimer: I am the author of
hcloud-upload-image
and the mentioned "extended packer templates". I also work at Hetzner, but this was done in my private time.How to use
If you have a Hetzner account, you can just follow along with the instructions.
Testing done
I have followed these steps myself while writing the docs to verify that they work.
changelog/
directory (user-facing change, bug fix, security fix, update)/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.