sequencer VS terraform-hcloud-kube-hetzner

I really love this idea in theory, and I believe that for some system, specially mature ones, it may work well. I see good documentation as a super power; it empowers readers and motivate people to understand more about the system without being caught in the weeds of reading the source.

The source has baggages, and the intent of every single function calls is not always evident. Writing documentation up-front can help direct the source, but this is a tug-of-war environment. Each affect the other in its own ways.

And for that reason, documentation driven development can be a real drag. You start writing documentation with the best intentions, everything works great for this first release. But 2 months down the road you need to modify something and it has a ripple effect on many of the things you documented. It's a non-negligible cost.

I've been working on this open-source tool(https://github.com/pier-oliviert/sequencer) and I've spent a lot of time on the documentation. And what I described above happened. I wanted to make a not-too-big change, and it required me to rewrite 30% of the documentation. I still love the documentation aspect of it, but it definitively has a cost.

First time I read about piku. I have no idea why, but the feeling of `git push` to initiate a deployment like piku does always felt magical to me. There's nothing simpler than that.

This is timely for me as well as I just open sourced (yesterday!) a project that is in the same space, but for Kubernetes (https://github.com/pier-oliviert/sequencer).

All of this to say, congrats! It looks great.

I like Epinio which does the same but on top of kubernetes. It is backed by Suse and lightweight compared to KNative (which is the basis of GCP CloudRun for example), but being kubernetes based still requires more Resources than dokku or Piku. I still prefer k8s due to the vast ecosystem of mature solutions. And I can still run everything on a single box, it just needs to be a bit bigger. The new Hetzner CX42 with 8 vCPUs, 16 GB of RAM, and 160 GB of disk space for € 16.40 a month (€ 0.0273 per hour) is sufficient, and with the Kube Hetzner Project I can set up a kubernetes cluster with auto updating microos in 5 minutes.

https://github.com/epinio/epinio/

https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne...

Hetzner starting with https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne..., plus registry using DigitalOcean.

However in the end my goto solution is k3s on hetzner cloud since it's got support for load balancers, ingress controllers with public IPS, persistent storage etc. It's cheaper than all the other cloud providers, although you need to run some code it doesn't have a 1 click solution. so I sold my hardware and used this https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner. I run it when I need a kube cluster and kill it by deleting the project.

You can look at this: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner

This whole setup is around 70euros per month, and I can enjoy usenet and torrent downloads of Linux ISOs to constantly peak at 1Gbps speed. All of this is HA with Kubernetes using this.

OpenSUSE MicroOS, we use it here. Another good option would be Fedora CoreOS

It's not even close to major public cloud providers, but this is my setup:

* https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne... (Terraform, Kubernetes bootstrap)

* Flux for CI

* nginx-ingress + Hetzner Loadbalancer (thanks to https://github.com/hetznercloud/hcloud-cloud-controller-mana...)

* Hetzner storage volumes (thanks to https://github.com/hetznercloud/csi-driver)

Kube-Hetzner supports Hetzner Cloud loadbalancers and volumes out of the box, though it also supports other components.