postgres-operator
postgresql_cluster
Our great sponsors
postgres-operator | postgresql_cluster | |
---|---|---|
33 | 9 | |
3,719 | 1,268 | |
1.9% | - | |
9.0 | 9.0 | |
8 days ago | 3 days ago | |
Go | Jinja | |
Apache License 2.0 | 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.
postgres-operator
- No disk space crashloop but pod healthy · Issue #3788 · CrunchyData/postgres-operator
- Deploying Postgres on Kubernetes in production
- Anyone using cloudnativepg in production?
-
Jolt v0.5.2 is available!
As for the Operators, I've been using Crunchy PGO, which is very high quality, and one of the most widely used. You can install it via Helm, or via OLM from OperatorHub. There are other good ones as well, but none that I have experience with. The only issue I've run into so far is I've had to disable TLS on the database cluster, as Prowlarr refused to connect with it for some reason (Radarr was fine). I still need to open an issue with the Prowlarr team about that, but I might switch to a service mesh for TLS anyway.
-
Can someone share experience configuring Highly Available PgSQL?
The Crunchy operator, seemingly like most (if not all) of the other Postgres operators (Zalando, KubeDB, and StackGres, etc.), is essentially a wrapper for Patroni. IMO if someone wanted a Patroni cluster, they would just build one. The point of an operator is to manage the cluster resources and node relationships, so why not have it take the role Patroni is filling here? It's already reaching into the nodes, obtaining status, managing the routing, etc., so why add the extra layer?
-
Questions about Kubernetes
On the topic of Postgres, you should look into an operator or Helm chart that can setup common things (like replication and auto-failover), such as Crunchy's Postgres operator, or consider using a "cloud-native" distributed database like CockroachDB (disclaimer: I am a Cockroach Labs employee) which has its own operator as well. Another word of warning, running stateful services, particularly mission critical databases, can require a lot of maintenance work (it's my full-time job), so unless this is for a hobby project, I would highly recommend you look into using a managed database offerring. Every major cloud provider and most database companies have one.
-
My girlfriend left me... I have a K8S cluster, argocd, longhorn, traefik, metallb, on 3 optiplex mff with proxmox... This is the start gentlemen, i'll post back in 1 year. This dashboard will be full my friends, I promise, see you in the rabbit hole o/
For postgres you can also have a look at PGO or bitnami helm chart
-
Databases on Kubernetes is fundamentally same as a database on a VM
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
-
Are you running databases on Kubernetes?
There is one particular client that have a somewhat big database 40-120gb (it change size over the year), and for that we used CrunchyData Postgres operator ( https://access.crunchydata.com/documentation/postgres-operator/v5/ ) we have no commercial relation with them, but oboi let me tell you the god send that thing is, this database in specific process massive data and it is distributed between several nodes in a read-write and read-only set, and let me tell you, it is amazing how easy it is to move things around, take backups, increase the capacity and a bunch of other goodies that operator bring. Give it a try.
- Do people use DBs as Pods?
postgresql_cluster
-
Automated Deployment of PostgreSQL Ha Clusters Anywhere
Creating a robust and reliable database cluster is often fraught with challenges.A manual deployment process can be fraught with risks, particularly for those who lack extensive experience. Even minor errors in configuration can drastically affect your database's performance and stability.
Recognizing this intricacy, many businesses choose to use cloud-based managed databases. These services offer convenience but not without limitations. These drawbacks can include being tied to a specific cloud provider and limited direct access to the database server for adjustments. These constraints can hinder your ability to tune your system and perform thorough performance analyses.
In response to these challenges, we've developed a project to make this process easier and more efficient. This project uses automation to streamline the deployment of High-Availability PostgreSQL Clusters. By doing so, it helps mitigate the risks involved with manual configuration and speeds up the deployment process.
Our solution caters to various deployment environments. It allows you to establish your cluster either in your own data center or in the cloud, providing a robust database solution similar to managed databases, but with you retaining full control.
Explore the project here: https://github.com/vitabaks/postgresql_cluster
-
Docker: Patroni + HAProxy + Etcd + PgBouncer
FYI: postgresql_cluster
-
Can someone share experience configuring Highly Available PgSQL?
HA postgres
- Toying with the idea of running Postgres instead of using RDS
- HaProxy/PgBouncer location.
- PostgreSQL High-Availability Cluster
-
Ask HN: Tips on hosting your own Postgres instance
If not Kubernetes, check out this: https://github.com/vitabaks/postgresql_cluster – Postgres + patroni + pgBouncer + WAL-G or pgBackRest + Netdata + more, managed by Ansible.
If you do want to use Kubernetes, then check out StackGres.io and https://github.com/zalando/postgres-operator
-
PostgreSQL High availability
Also check PostgreSQL High-Availability Cluster (based on "Patroni" and "DCS(etcd)"). Automating deployment with Ansible.
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.
patroni - A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
pg_auto_failover - Postgres extension and service for automated failover and high-availability
longhorn - Cloud-Native distributed storage built on and for Kubernetes
pgcat - PostgreSQL pooler with sharding, load balancing and failover support.
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
embedded-postgres - Run a real Postgres database locally on Linux, OSX or Windows as part of another Go application or test
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
top500-benchmark - Automated Top500 benchmark for clusters or single nodes.
k3s - Lightweight Kubernetes
pigsty - Battery-Included PostgreSQL Distro as a Free RDS Alternative