postgres-operator
postgres-operator
postgres-operator | postgres-operator | |
---|---|---|
6 | 34 | |
179 | 4,040 | |
1.7% | 0.9% | |
5.4 | 9.3 | |
6 months ago | 4 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
-
Jolt v0.5.2 is available!
I found a couple of those Postgres operators, like the movetokube/postgres-operator but I honestly can't tell which of them are any good. Do you have any experience with them? I also would need something for MinIO, since I'm able to use Terraform to create databases, buckets and then spin up the app. It's a really comfortable process albeit I do prefer GitOps.
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
Not everything carries over from Terraform to GitOps but with that said check out this operator that lets you provision an existing postgres database.
-
Database for homelab - in or out of cluster?
On my list is the external postgres operator to provision databases on the external postgres instance, similar to using democratic-csi for providing volumes on the TrueNAS host. https://github.com/movetokube/postgres-operator
-
Is there an operator/controller for Kubernetes that allows me to create Postgres roles and databases with CRDs?
Others have mentioned some great operators for managing in-cluster postgres databases, but if you're looking to manage external or previously existing databases: https://github.com/movetokube/postgres-operator
-
If I set up a home K3s setup.. how often am I going to have to...
That is my plan, too. I have the External Postgres Server Operator on my list of thing to try out. Does anyone have experience with it already?
-
Operator to Replicate Kubernetes ImagePullSecrets to all namespaces
Here is an example of an operator that creates databases: https://github.com/movetokube/postgres-operator
postgres-operator
- Show HN: Serverless Postgres
- 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.
What are some alternatives?
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
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
wireguard-operator - Painless deployment of wireguard on kubernetes
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
operator - Simple Kubernetes Operator for MinIO clusters :computer:
QuestDB - QuestDB is a high performance, open-source, time-series database
pull-secret-operator - Copy pull secrets from one namespace into one or more other namespaces
longhorn - Cloud-Native distributed storage built on and for Kubernetes
kubegres - Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.
registry-creds - Replicate Kubernetes ImagePullSecrets to all namespaces
postgres - Unmodified Postgres with some useful plugins