Recent searches
Search options
Anyone know of a VPS hosting provider with first-class support for Fedora CoreOS and a decent API?
I wish Hetzner supported CoreOS but it doesn’t.
Would love to get the small web stuff on a solid foundation (re: self-updating/zero-maintenance) but looks like I have to stick to Ubuntu for now; at least to start with as I can’t find a Hetzner-like experience (they set up supported images in literally seconds & have an excellent API/low prices) that supports CoreOS.
Opened a CoreOS platform request for Hetzner. Let’s see if it goes anywhere :)
@aral i guess all hetzner would need is a cloud-init image. https://github.com/coreos/coreos-cloudinit points to https://github.com/coreos/ignition and i don't know if the latter is compatible with the former, but that's what i would link the hetzner-support to 
@aral I sure hope Hetzner moves to Ignition as that seems to be the new standard and that could also open the path to Fedora CoreOS or Suse MicroOS. In the meantime the only approach i know of is using a rescue image and coreos-installer from the inside. You can automate all that stuff but its clearly a much greater effort than just a few clicks on the cloud console. A little trick if you do things manually: make a snapshot after installing before booting and use a remote ignition file.
@cardes I did run a few tests but booting from a snapshot is too slow for my use case (I want to get people set up with their own sites in under a minute to match/exceed the experience of setting up a social media account on a centralised surveillance capitalist like Facebook, etc.) :)
@aral How much isolation do you need for that? Just a hunch without knowing all the deatails: There are ways to fully isolate namespaces in kubernetes, hetzner csi provides encryption and regarding network policy and traffic routing you could possibly use one ipv6 address out of their large /64 subnets for every namespace aka person on the platform.
@cardes Interesting thought but I’m trying to keep it as plain vanilla as possible so it can as easily be deployed on a single-board computer at home using almost the same process. And I’d like it to be as portable between providers as possible so I’m trying to keep deployment as standards-based and uncomplicated as possible.
@cardes (Really appreciate the feedback/thoughts though and will definitely have a think about the points you raise.) :)
@aral I read your article on the small web and understand that using a single topology (aka kubernetes cluster db) would be the opposite of what you're trying to achieve. Reflecting a bit on your approach without knowing the technical details: Is it inside your scope to provide more than one application per person and vm? If so the container approach would take the lease ressources and management overhead i can think of. It also opens the door to many apps per person and server (think families)