PostgreSQL: Kubegres is available as open source

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?

I love this sort of thing. Something I appreciate is looking through the resulting YAML config at the best practices and rich experience by the team that wrote it.<p>It reminds me of receiving &quot;golden images&quot; from vendors with a precisely best-practice install and configuration of their software.

I&#x27;ve interacted with the kubegres creator and maintainer in the past and it was a good experience, wishing them luck giving Zalando and Crunchy operators a run for their money.<p>See <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;PostgreSQL&#x2F;comments&#x2F;mqrsbn&#x2F;kubegres_is_a_kubernetes_operator_for_postgresql&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;PostgreSQL&#x2F;comments&#x2F;mqrsbn&#x2F;kubegres...</a>

generally hope &#x27;self hosting your DB&#x27; becomes a spectrum rather than a choice to use or not use RDS<p>it&#x27;s frustrating that you can&#x27;t use something like timescaledb on a paas (i.e. that timescale needs to manage their own instances to operate their business).<p>not sure kube is the cheapest or safest way to run a DB, but there should be something platform-like for hosting persistent data

Any comparison with the other solutions? (e.g. the ones from <a href="https:&#x2F;&#x2F;blog.flant.com&#x2F;comparing-kubernetes-operators-for-postgresql&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.flant.com&#x2F;comparing-kubernetes-operators-for-po...</a>)

Does Kubegres works with any TCP proxy, and if does - is there any recommendations which one? Running ingress via Load Balancer is quite costly option in cloud context. At the moment is seems that nodeport is only realistic alternative.

I wonder how is this compared to Stolon <a href="https:&#x2F;&#x2F;github.com&#x2F;sorintlab&#x2F;stolon" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;sorintlab&#x2F;stolon</a>?

Where I can read how modern k8s deals with persistent storage? It looks like after pg cluster shutdown you lose all data.

Is there something new here from the April announcement? Did something change?

From what I understand, you still have to solve the usual hard challenges of HA:<p>1) Applications reconnecting to the new Postgres master and retrying queries<p>2) Persistent storage available in multiple AZs or regions for your Postgres pods (impossible on AWS for example)

How does this compare to cockroach?

So I can create 2 servers running kubegres, kill one and then all data should be intact? And no downtime?

Is it logical for AWS to offer RDS over K8s?