postgres-operator
percona-postgresql-operator
Our great sponsors
| postgres-operator | percona-postgresql-operator | |
|---|---|---|
| 36 | 4 | |
| 3,947 | 240 | |
| 2.3% | 7.1% | |
| 8.6 | 9.0 | |
| 21 days ago | 7 days ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postgres-operator
-
Run PostgreSQL. The Kubernetes Way
yes, precisely. It's UI part that's broken, which cannot list snapshots. Issue is here, no fix since 2020, sadly: https://github.com/zalando/postgres-operator/issues/937
- Deploying Postgres on Kubernetes in production
-
Why PostgreSQL High Availability Matters and How to Achieve It
one of the solutions which made it pretty simple for us to run postgresql in a ha environment (mostly in k8s, but works standalone as well) is zalandos patroni: https://github.com/zalando/patroni it's really solid and worked for us for a few years already.
or for k8s their operator: https://github.com/zalando/postgres-operator (docker image: https://github.com/zalando/spilo) we've also tried other operators which were easier to get started, but they failed miserably (crunchyrolls operator is basically based on the zalando one)
-
[Kubernetes] Comment déployez-vous un cluster Postgres sur Kubernetes en 2022?
Zalando / Postgres-Operator
-
What are you using to run Postgres?
Somewhere between here and here i found out about that.
-
Databases on Kubernetes is fundamentally same as a database on a VM
And that repo you linked to has 1846 issues, 161 open. Which doesn't seem extraordinary based on my limited exposure to k8s.
Another example: https://github.com/zalando/postgres-operator/issues with 445 open issues. Why?
Maybe I'm wrong and this is all a good sign of progress, but my impression is that the entire k8s ecosystem is held together with reused duct tape.
-
Features I'd Like in PostgreSQL
In Kubernetes a service call end an operator watches for CRD specifying databases to be created and manages upgrade and backs for those databases.
-
Any self hostable postgres clustering, replication and fail over system?
You could fire-up `k3s` or `microk8s` or something of that ilk and run https://github.com/zalando/postgres-operator
-
Just Use Postgres for Everything
My favorite route right now is running a postgres operator on Kubernetes & letting it do all the work for me.
Zalando's operator use Patroni under the hood, to create a cluster over streaming replication. It also has Spilo, which orchestrates pg_basebackup or WAL-E for point-in-time backup. https://github.com/zalando/postgres-operator#postgresql-feat...
CrunchyData operator seems to have built their own streaming replication system coordinated by Raft. https://access.crunchydata.com/documentation/postgres-operat...
-
Best way for high-available database at home?
I don't have much experience with HA databases, so I can't really decide which way I should go. I found a postgres-operator to be run on a kubernetes cluster: https://github.com/zalando/postgres-operator. And a guide to setup postgres HA with patroni: https://arctype.com/blog/postgres-patroni/
percona-postgresql-operator
-
Is anyone using postgres on kubernetes?
I have made very good experiences with operators from percona. Feel free to try it https://github.com/percona/percona-postgresql-operator
-
Pgo: The Postgres operator from crunchy data
CEO Percona Here.
It is more than "Percona Thinks" We have number of customers who started using Crunchy Kubernetes Operator based solution thinking it is Open Source and were contacted by Crunchy Sales team to indicate they need subscription to use it.
This was one of the reasons for them to move to Percona Operator for PostgreSQL which does not require any commercial relationship with Percona to use in practice and completely Open Source
https://www.percona.com/doc/kubernetes-operator-for-postgres...
- Have you ever used PostgreSQL on Kubernetes in production?
What are some alternatives?
kubegres - Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
cloudnative-pg - CloudNativePG is a comprehensive platform designed to seamlessly manage PostgreSQL databases within Kubernetes environments, covering the entire operational lifecycle from initial deployment to ongoing maintenance
helm-charts - A curated set of Helm charts brought to you by codecentric
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
postgres - Unmodified Postgres with some useful plugins
chaos-mesh - A Chaos Engineering Platform for Kubernetes.
operator-sdk - SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.
supabase - The open source Firebase alternative.
lvm-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend LVM2 data storage stack.