kubegres VS cluster-template

A good comparison with other operators here [2022]: https://blog.palark.com/cloudnativepg-and-other-kubernetes-o...

Personally I've only used Kubegres (https://www.kubegres.io/), which didn't even make the above list. It's ok for a personal project.

All k8s solutions for postgres take subtly different approaches. It seems that they've all converged on the Operator pattern. The basics are easy: run a database process which persists data to a cloud disk of your choice. The hard parts are how to update, migrate, backup, restore, monitor, failover, replicate, etc. These kubernetes "operators" promise to fulfill the role of a DBA but, just like hiring a DBA, it requires buy-in to their approach.

Reactive-Tech / Kubegres (opérateur)

I like https://www.kubegres.io, it takes a little getting used to how it works. I probably wouldn't use it for a huge database, but for things under a few TB it works great.

I don't know if you're using Kubernetes, but Kubegres is great for self hosting postgres on a cluster.

Any experience with https://www.kubegres.io/ ?

How does this compare with something like kubegres?

https://www.kubegres.io/

https://www.kubegres.io/ has worked well for me. You can use custom images, provided they follow the conventions of the official postgres image. I haven't tried a major-version upgrade yet - my impression is that it will probably be a bit painful and involve some downtime and manual ops.

Some of the more advanced operators might better handle the upgrade problem? But in general, I've been happy with Kubegres for a ~10GB database with low traffic.

There are some great operators out there that make deployment and management easy. I use kubegres managed with pgadmin and it has been working well for me.

reactive-tech/kubegres (operator)

k8s is a lot easier for homelabs than it used to be, and imo it's quicker than nix for building a declarative homelab. templates like this one can deploy a cluster in a few hours: https://github.com/onedr0p/cluster-template

here's my home assistant deployment as a single file: https://github.com/pl4nty/homelab/blob/main/kubernetes/clust...

I deliberately nuked my onprem cluster a few weeks ago, and was fully restored within 2 hours (including host OS reinstalls). and most of that was waiting for backup restores over my slow internet connection

example repo: https://github.com/onedr0p/flux-cluster-template

Magical setups like this often get a lot of bad rap, but if you already understand Ansible and know Linux etc, you might find this repo a good start to building out your own cluster using gitops: https://github.com/onedr0p/flux-cluster-template

more of an end-to-end solution than a build-it-yourself, but this was a huge help in my understanding of k8s and the other tech like gitops - https://github.com/onedr0p/flux-cluster-template

idk how it'd scale for a larger operation, but flux+sops+age has worked great for me. based on https://github.com/onedr0p/flux-cluster-template

Here is a really good and VERY thorough example of pulling that all together: https://github.com/onedr0p/flux-cluster-template