[dvfjsdhgfv]

> Hetzner volumes are, in my experience, too slow for a production database. While you may in the past have had a good experience running customer-facing databases on AWS EBS, with Hetzner's volumes we were seeing >50ms of IOWAIT with very low IOPS.

There is a surprisingly easy way to address this issue: use (ridiculously cheap) Hetzner metal machines as nodes. The ones with nvme storage offer excellent performance for dbs and often have generous amounts of RAM. I'd go as far as to say you'd be better off to invest in two or more beefy bare metal machines for a master-replica(s) setup rather than run the db on k8s.

If you don't want to be bothered with the setup, you can use one of many modern packages such as Pigsty: https://pigsty.cc/ (not affiliated but a huge fan).

[threeseed]

There are plenty of options for running a database on Kubernetes whilst using local NVMe storage.

There are just pinning the database pods to specific nodes and using a LocalPathProvisioner or distributed solutions like JuiceFS, OpenEBS etc.

[BillFranklin]

Thanks, hadn’t heard of pigsty. As you say, I had to use nvme ssds for the dbs, the performance is pretty good so I didn’t look to get metal nodes.

[lucasrattz]

I've had great experiences with using the bare metal server's local storage.

This is the guide I wrote for our customers: https://syself.com/docs/hetzner/apalla/how-to-guides/storage...

[gourneau]

Thanks for the Pigsty link. I have been a big fan of running Postgres on metal machines.