Live data from Hacker News

Pgo: The Postgres operator from crunchy data

github.com

1–10 of 38 posts

Re: Pgo: The Postgres operator from crunchy data

#3

Another popular alternative: https://github.com/zalando/postgres-operator New player from Enterprise DB: https://github.com/cloudnative-pg/cloudnative-pg

Worth noting that the Crunchy operator is based on Patroni, which is maintained by Zalando.

Re: Pgo: The Postgres operator from crunchy data

#4

Another popular alternative: https://github.com/zalando/postgres-operator New player from Enterprise DB: https://github.com/cloudnative-pg/cloudnative-pg

https://www.percona.com/doc/kubernetes-operator-for-postgres...

Percona also has a PG operator.

Re: Pgo: The Postgres operator from crunchy data

#5

Another popular alternative: https://github.com/zalando/postgres-operator New player from Enterprise DB: https://github.com/cloudnative-pg/cloudnative-pg

+1 for cnpg - I couldn't get any of the other operators to work well for me, but cnpg has been a blast.

Re: Pgo: The Postgres operator from crunchy data

#6
https://www.crunchydata.com/developers/terms-of-use

Before using Crunchy Data, I'd read their terms of use.

"without an active Crunchy Data Support Subscription or other signed written agreement with Crunchy Data are not intended for... using the services provided under the Program (or any part of the services) for a production environment, production applications or with production data"

https://hub.docker.com/r/crunchydata/crunchy-postgres

If you look at their Docker Hub images, you'll see that they're provided under the terms of use of the Crunchy Data developer program which means you can't use them in production without an active subscription.

Maybe I'm reading it wrong, but if that's the case Crunchy Data should definitely change their terms of service.

https://www.percona.com/blog/2021/05/26/percona-distribution...

Percona certainly seems to think you can't use the Crunchy Data images in production saying, "CrunchyData container images are provided under Crunchy Data Developer Program, which means that without an active contract they could not be used for production."

Re: Pgo: The Postgres operator from crunchy data

#7
post #6

https://www.crunchydata.com/developers/terms-of-use Before using Crunchy Data, I'd read their terms of use. "without an active Crunchy Data Support Subscription or other signed written agreement with Crunchy Data are not intended for... using the services provided under the Program (or any part of the services) for a production environment, production applications or with production data" https://hub.docker.com/r/cru…

I think this is more of the disclaimer that they are not responsible to any damage to your production systems if you do not use their support. That's why the wording is "are not intended for..." and not "you are prohibited from..."

Re: Pgo: The Postgres operator from crunchy data

#8
I used this in the past. Helped a lot with provisioning micro-pg-clusters.

But honestly, the project always felt like a one-man-show, some (realy great) dev had a working set of scripts and kubernetized / operatorized it, but the whole thing feels hacky as hell.

I'd still give a try if I ever needed postgresql again, but I would also know that I need to implement (again) my set of scripts and hacks on top of it.

Re: Pgo: The Postgres operator from crunchy data

#9

Another popular alternative: https://github.com/zalando/postgres-operator New player from Enterprise DB: https://github.com/cloudnative-pg/cloudnative-pg

If building a list of alternatives, let me do a shameless plug for StackGres [1], the Postgres platform for Kubernetes with a fully featured Web Console, AMD64 and ARM64 support and more than a hundred available Postgres extensions [2]. Fully open source, no usage restrictions.

[1] https://stackgres.io/

[2] https://stackgres.io/extensions/

Disclaimer: founder of the project.

Post reply on HN