It made me sad to see that Hetzner had discontinued the FreeBSD rescue system. But it seems to be correct: https://community.hetzner.com/tutorials/freebsd-openzfs-via-...
How much did it really cost them to have the mfsbsd image available?
It made me sad to see that Hetzner had discontinued the FreeBSD rescue system. But it seems to be correct: https://community.hetzner.com/tutorials/freebsd-openzfs-via-...
How much did it really cost them to have the mfsbsd image available?
I have some notes on doing that, including notes on my setup for disk encryption with FreeBSD on Hetzner:
https://gist.github.com/ctsrc/9a72bc9a0229496aab5e4d3745af0b...
This is of course easier (although the KVM software is a heap of proprietary arse with a web interface or ancient Java blob), but if you are truly paranoid you will have to trust the Hetzner staff and their software stack not to bring something undesired along with your provided image.
But it is not the initial setup I am really worried about. It is those fan meet fecies moments. Being able to respond to a situation instantly. Mfsbsd was a godsend.
Trying to fix problems on one OSis from a different OS is a much harder issue. Especially under pressure.
I would much rather have seen they added OpenBSD to their PXE environment. Just the vanilla stuff - no fancy optimizations.
I've actually built a small tool that has the UX of regular SSH but under the hood reboots into rescue, configures the keys and opens an SSH session. Once you close it, it reboots back into regular mode.
I've wrapped that tool again to then build a tool that takes just an ignition config and automatically images a hetzner server with fedora coreos using that config.
You could easily build your own tool that reboots into rescue, installs a VM, mounts all the necessary devices, boots the OS image, and exposes the serial console of that VM to you.
It took me a while to learn to love Hetzner's solution, but I prefer it over having to use shitty proprietary KVMs.