patroni
postgres-operator
Our great sponsors
patroni | postgres-operator | |
---|---|---|
19 | 36 | |
6,137 | 3,912 | |
1.8% | 2.8% | |
9.2 | 8.6 | |
4 days ago | 11 days ago | |
Python | Go | |
MIT License | MIT License |
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.
patroni
-
How to create postgres cluster in docker swarm?
We have been using stolon + consul for years without issue in our swarm environments. It may also be possible with patroni.
-
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)
-
Docker: Patroni + HAProxy + Etcd + PgBouncer
Hello. I am currently using this docker-compose model from Zalando repository. It does not include PgBouncer in its architecture by default. I've been trying to find a containerized implementation involving Patroni, HAProxy, Etcd and PgBouncer. I didn't find anything solid so far.
-
Can someone share experience configuring Highly Available PgSQL?
General purpose: Patroni - Set up your own etcd + HAProxy + Patroni + Postgres components and it'll generally manage itself after that.
- Any self hostable postgres clustering, replication and fail over system?
-
GCP Cloud SQL Migration without outage?
This is why I always recommend using a postgres proxy so you can point it to different database servers as you stand them up. AWS does this by default but GCP doesn’t yet, so you have to have your own Postgres proxy (e.g https://github.com/CrunchyData/crunchy-proxy) or move to an HA Postgres setup like Patroni that has streaming replication (https://github.com/zalando/patroni).
- PostgreSQL 14 Released
- Vitess 11
-
How can I check the load of the PostgreSQL container?
Want a tool for increasing the durability of your DB? I suggest running postgres via systemd, or failing that, start-stop-daemon. To get even more robust, look in to something like setting up pgbouncer in front of haproxy in front of a set of read-only replica PG instances running in either logical or streaming replication. To get even MORE robust, I suggest Patroni for high-availability PG.
-
PostgreSQL High availability
see here - https://github.com/zalando/patroni
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/
What are some alternatives?
pg_auto_failover - Postgres extension and service for automated failover and high-availability
stolon - PostgreSQL cloud native High Availability and more.
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.
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
cloudnative-pg - CloudNativePG is a Kubernetes operator that covers the full lifecycle of a PostgreSQL database cluster with a primary/standby architecture, using native streaming replication
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).
postgresql_cluster - PostgreSQL High-Availability Cluster (based on "Patroni" and DCS "etcd" or "consul"). Automating with Ansible.
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