postgres-operator

I always assumed crunchy was using their own operator for their managed offering. Is that not the case? https://github.com/CrunchyData/postgres-operator

How does this compare to Neon[1], Crunchy PostgreSQL for Kubernetes[2], and Citus[3]? [1] https://neon.tech / https://github.com/neondatabase/neon [2] https://access.crunchydata.com/documentation/postgres-operat... / https://github.com/CrunchyData/postgres-operator [3] https://www.citusdata.com / https://github.com/citusdata/citus

Let's say a new Kubernetes version comes out in April. In November, as everything works perfectly well, you decide to install a Postgres operator on it. Bummer, it doesn't work. It's not a huge issue, you just wait until the bug is resolved (already done[0]), but it's just one of these tiny things that I don't get when running Postrges natively. And I'm saying this as a big fan of Crunchy Data running some production loads on it without a failure for quite some time now. [0] https://github.com/CrunchyData/postgres-operator/issues/3476

I agree that the developer program ToS is written in a confusing manner and suggests that you can't use it all for production without a license. I expect that to be intentional: if the impression you get is that you can't even use their software in production, it's much less likely that you will do so with the impression that there is any support, warranty, or endorsement of such use. [EDIT: I made an error, I originally said that it was explicit about no license being granted for the software, but that was about things like no license for service marks and trade names.] On the other hand, there is a license for postgres-operator and it looks like Apache 2.0: https://github.com/CrunchyData/postgres-operator/blob/master... For what's being distributed in their Docker container image, I imagine it depends on what they're actually distribut

The keyword you're looking for here is Operator [1]. Kubernetes Operators are custom resources (e.g. Database, Load Balancer, ACME Certificate Entry) that manage themselves via a reconciliation loop. If you're looking for a specific piece of infrastructure, search for `<YOUR_TECHNOLOGY> + "operator"`, (e.g. "Postgres Operator", "Kafka Operator", etc...). Once you find an operator for the piece of infrastructure you need, just follow their instructions on how to set it up and configure it. Learning about how operators work is pretty neat and writing your own is fairly simple if you don't find an operator for your use case. Personally I run my personal cluster on K3s [2], secure it with cert-manager [3] and route traffic via the Traefik Operator [4]. Right now I use Litestream for all of my DB needs, but I've heard good things about the Pos

Not really replying to your question. But recently I got the occasion to work with https://github.com/CrunchyData/postgres-operator . It's a bit rough around the edges wit the v5, which is very recent, but overall I was really happy with it. I am still not using it in production but it's on the way.

> Incredible delay between postgres versions To be fair, it looks like GCP supported Postgres 13 (Nov 5, 2020) before AWS did (Nov 27, 2020) and AWS currently marks Postgres 13 as a preview. Maybe GCP had a large initial engineer-cost to support multiple versions of Postgres and now the incremental cost to add new versions is small? > It's just a lot of money to pay for a crashy, outdated version of Postgres. Have you looked at other options? I'm evaluating GCP SQL and the comments in this thread are scary. Seems like Aiven might be a good way to go. I've also briefly looked at CrunchyData's Postgres Operator [1] for Kubernetes but it's a lot of complexity I don't really want. [1]: https://github.com/CrunchyData/postgres-operator

There is also https://github.com/CrunchyData/postgres-operator which seems more mature.

If you are using a managed kubernetes cluster from a cloud provider you mostly don't need to worry about these sorts of things. If you're not, and deploying to bare metal, the main things you need to worry about are: load balancers, storage & monitoring. If you're large enough that you can effectively run kube on bare metal you probably have enterprise solutions for load balacing [0], storage [1] & monitoring your applications that you've already validated as being secure/stable. If you want to go all out you can also grab an operator to manage rolling out databases for you (postgres [2], mongo, etc). A lot of the complexity people bump into with kube is really poorly planned out tools like Istio that have way too many features, a very overly complex mode of operation (out of the box it breaks CronJobs!!!), and very sub-standard community

This k8s operator advertises production-grade auto-failover auto-healing replicas - basically what MongoDB - but built on postgres: https://github.com/CrunchyData/postgres-operator And looking at this table, basically the future seems to be WAL shipping anyway ( https://www.postgresql.org/docs/13/different-replication-sol... )

Exactly. The frameworks that the article describes know how to run say Cassandra or Spark, but you can do the same thing in Kubernetes using TPRs or CRDs with operators: [0]https://github.com/coreos/prometheus-operator [1]https://github.com/coreos/etcd-operator [2]https://github.com/huawei-cloudfederation/redis-operator [3]https://github.com/CrunchyData/postgres-operator [4]https://github.com/krallistic/kafka-operator [5]https://github.com/pegerto/cassandra-operator

https://github.com/CrunchyData/postgres-operator is the most promising thing I've seen lately.

People are working on things on-top of Kubernetes, such as https://github.com/CrunchyData/postgres-operator