PostgreSQL: Kubegres is available as open source

It seems like the big difference is that it uses the standard PostgreSQL Docker images and doesn't bundle together as many things as Zalando or Crunchy Data. They'd likely argue that makes it easier to learn and a smaller surface area for attacks or things to go wrong.

Crunchy Data includes lots of add-ons like pgBouncer, pgAdmin 4, pgMonitor, and a bunch more. That might be a lot for someone that just wants a simple replicated PostgreSQL setup.

But I don't know much about Kubegress. It's repository has only 67 commits and 3 contributors so it's not as widely used as something like Crunchy Data or Zalando which have thousands of commits and hundreds of contributors. Likewise, Crunchy Data and Zalando both have 2,000+ stars compared to 387 for Kubegress.

That's not necessarily a sign of quality and part of that could be that Kubegress had a bunch of development before being open-sourced, that being later to the game makes it harder to build community, and that creating something simple might not require as many commits since you're creating something simple.

I use https://rook.io/ to set storage up usually, they have a bunch of different options and good documentation.

Mind you, no clustered system can provide you zero downtime and zero data loss without essentially the same constraints. If you have an unplanned failure, there's going to be a blip somewhere. It's up to the rest of the system to recover from it gracefully.

When configuring any kind of cluster involving data (especially one that's supposed to recover automatically from faults), make sure you understand how it behaves and adjust for your application, because quite often the default configurations might accept some data loss in unplanned failover or conflict scenarios.

https://aws.amazon.com/blogs/opensource/aws-service-operator... https://github.com/aws-controllers-k8s/community