patroni
stolon-chart
patroni | stolon-chart | |
---|---|---|
20 | 1 | |
6,252 | 105 | |
1.8% | - | |
9.1 | 0.0 | |
4 days ago | over 3 years ago | |
Python | Smarty | |
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
-
Ask HN: Are there any open source forks of nomad smd consul?
> I think etcd is basically a k8s only project now
I hate etcd with the best of them, but etcd is used in a lot more places than just kubernetes:
https://github.com/apache/apisix/blob/master/docs/en/latest/...
https://github.com/traefik/traefik#:~:text=Etcd,
https://github.com/zalando/patroni#patroni-a-template-for-po...
https://github.com/purpleidea/mgmt/tree/0.0.26/etcd (this one shows up on HN quite a bit)
https://github.com/sorintlab/stolon#features
It's actually one of the major reasons I wouldn't touch those projects
-
Citus is not ACID but Eventually Consistent
Citus doesn't provide fault tolerance. Each shard is a monolithic PostgreSQL. To reduce downtime on failures, you can protect each shard with a standby database. As this is a complex configuration, Patroni can help. For this lab I'll use the Citus+Patroni docker-compose-citus.yml from https://github.com/zalando/patroni.git:
-
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.
- Patroni Version 3.0.0 Released
- Any self hostable postgres clustering, replication and fail over system?
-
Postgresql HA using repmgr and Keepalived
I don't have a great answer for you except that it sounds like you are trying to create your own version of patroni. Is there a good reason to not just use patroni?
-
Testing Patroni strict synchronous mode 👉🏻 you must handle invisible commit and read split brain
git clone https://github.com/zalando/patroni.git cd patroni docker build -t patroni . docker-compose up -d
stolon-chart
-
Lessons learned after migrating from Heroku to a Kubernetes cluster
I am using the Stolon Helm chart : https://github.com/lwolf/stolon-chart I was advised on the topic by the consultant I mentioned in the article. I am not 100% confident about managing the database ourselves, but so far so good... and I am very confident in Postgres overall so that balances the matter. Stolon itself seems stable and mature. We tried using Google CloudSQL first (we are hosted on GKE) but we decided against it in the end because our strategy is to be platform-independent and self-contained. Also, we ran into issues related to users, admins and the ability to create extensions (I can't exactly recall what it was, just that it was a bummer).
What are some alternatives?
pg_auto_failover - Postgres extension and service for automated failover and high-availability
traefik-helm-chart - Traefik Proxy Helm Chart
stolon - PostgreSQL cloud native High Availability and more.
charts - HAProxy Ingress helm charts
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.
charts - TrueNAS SCALE Apps Catalogs & Charts
postgresql_cluster - PostgreSQL High-Availability Cluster (based on "Patroni" and DCS "etcd" or "consul"). Automating with Ansible.
crunchy-proxy - PostgreSQL Connection Proxy by Crunchy Data (beta)
shadowsocks-helm-chart - a Helm chart for Shadowsocks
pgvector - Open-source vector similarity search for Postgres
clearml-helm-charts - Helm chart repository for the new unified way to deploy ClearML on Kubernetes. ClearML - Auto-Magical CI/CD to streamline your AI workload. Experiment Management, Data Management, Pipeline, Orchestration, Scheduling & Serving in one MLOps/LLMOps solution