opensearch-k8s-operator VS kubegres

Or use the OpenSearch Kubernetes Operator to spin up and manage your new clusters: https://github.com/Opster/opensearch-k8s-operator

The Kubernetes Operator for OpenSearch is here! The open-source Apache 2.0 Operator is used for automating the deployment, provisioning, management, and orchestration of OpenSearch clusters and OpenSearch dashboards. Check out the github repo and give it a spin here: https://github.com/Opster/opensearch-k8s-operator

Because of these limitations and the ones others highlighted, you might be better off staying self-managed. A Kubernetes deployment could be a good alternative to the managed service route. You can check out this K8s Operator: https://github.com/Opster/opensearch-k8s-operator

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)