News for hackers. Stuff that matters.
Re:Run PostgreSQL. The Kubernetes Way by oooyay on Friday September 22, 2023 @09:43PM (#37619921)
I run a stateful metadata cache on Kubernetes with a StatefulSet and EBS as block storage. It runs SQLite just fine.

As for the "setting up Kubernetes" comment, I think that could be true of Kubernetes years ago. Nowadays Platform Engineers generally build on its capabilities continually, and by the time a user is using it to schedule network, compute, and storage the setup for an application maybe takes a day or so without a template. Most of the platform engineering work I've done on Kubernetes had much more to do with lifecycle management than paining myself over initial provisioning.

Re:Run PostgreSQL. The Kubernetes Way by antonvs on Saturday September 23, 2023 @03:43AM (#37621399)
> EBS as block storage

We do the equivalent on GCP. A lot of the criticism about Kubernetes storage seems to come from people using it onprem.

In that context, I can well imagine that it's a PITA to set up well. As rjzzleep commented in this thread:

> Whenever someone runs Kubernetes onprem I tell them to buy a TrueNAS or another cheap SAN. A cheap SAN costs as much as a DevOps expert setting up your Ceph infrastructure and a lot less when you actually run into issues with that software defined storage solution. Once you do that Kubernetes is actually quite nice

Re:Run PostgreSQL. The Kubernetes Way by ahoka on Saturday September 23, 2023 @04:04AM (#37621476)
Why do you use a StatefulSet? I assume every instance has it own volume with its own sqlite and that backs the cache. Why not just Deployment? Failover would be easier in that case.
Re:Run PostgreSQL. The Kubernetes Way by oooyay on Saturday September 23, 2023 @11:38AM (#37624235)
I scale it vertically. Cache refresh is non optimal and takes a few hours. I could make it better by having the instances talk, but frankly the service may never actually need to scale. It can handle thousands of rps off that single container.