3 ms·
Since this is just a PR announcement by a third-party posted on an official PostgreSQL page: what is the difference between this and established PostgreSQL oper
by pronik 5y ago
Since this is just a PR announcement by a third-party posted on an official PostgreSQL page: what is the difference between this and established PostgreSQL operators by Zalando and CrunchyData?
- deleted 5y ago[deleted]
- mdasen 5y agoI was wondering this too and found: https://www.kubegres.io/#kubegres_compared https://www.kubegres.io/#kubegres_compared 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.
- coding123 5y agoThen again you don't need a whole lot to have those features coupled with k8s. Kiss solution.
- Turbots 5y agoVMware has a very well supported Postgres K8S operator as well: https://tanzu.vmware.com/sql#sql-with-kubernetes https://tanzu.vmware.com/sql#sql-with-kubernetes