postgres-operator
democratic-csi
Our great sponsors
postgres-operator | democratic-csi | |
---|---|---|
33 | 14 | |
3,715 | 724 | |
1.8% | 4.0% | |
9.0 | 5.6 | |
3 days ago | 23 days ago | |
Go | JavaScript | |
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?
democratic-csi
-
NVMe-OF with Non-SSD Drives: Worth the Switch?
The interface software regarding is not a worry of mine, as democratic-csi does the storage management for me, thus the compatibility it is not limited to the application using the storage per se, as this is handled by Kubernete's CSI drivers, being application-agnostic when utilizing the storage provided.My main worry is not latency, but rather RAM
-
There doesn't seam to be any good distributed block storage for Kubernetes
Check out https://github.com/democratic-csi/democratic-csi
-
Kubernetes dev homelab & NAS
in k3s, i'm using https://github.com/democratic-csi/democratic-csi (was using iSCSI before, now everything is NFS)
-
Which block storage solution to self host ?
Have you checked this out? GitHub democratic-csi I have yet to test this in my @home K8s cluster. It supports iSCSI volume management for FreeNAS, Synology and other CSI backends.
-
What's the best way to utilize a NAS with Docker services on separate machine?
If you ever migrate from docker up to kubernetes, then take a look into democratic-csi. For a modest homelab, it is a valid option (said from somebody who manages a small homelab and plays around with kubernetes).
-
Optimizing zvols for ext4 use?
For persistent storage have you looked into using TrueNAS with a CSI provider with your container orchestrator? I'm assuming your orchestrator is Nomad or Kubernetes.
-
You need Rancher on truenas scal
Yes, Rancher does support FreeNAS, TrueNAS. and Scale using the storage class provider https://github.com/democratic-csi/democratic-csi It's important to remember Rancher is the server. And in this case, you need to ask the question does the k8s cluster that Rancher is managing support this storage class provider? If you are using RKE the answer is Yes.
-
From Docker (-Compose) to K3s?
I use https://github.com/democratic-csi/democratic-csi to mount nfs/iscsi shares (and manage the shares) from my SAN (truenas box).
-
iSCSI and multiple pods - does it work?
iSCSI with democratic-csi (https://github.com/democratic-csi/democratic-csi) works great for me on truenas. I use iSCSI for any PVs that don't need to be shared and NFS for anything I'd like to share between different pods (like movies, music).
-
Building a "complete" cluster locally
Storage - democratic-csi looked the most promising, it has worked well so far. I am using zfs-generic-iscsi against an Ubuntu 20.04 storage server. I also tried zfs-generic-nfs and it worked successfully with the caveat of having to deal with NFS file permissions.
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.
truenas-csp - TrueNAS Container Storage Provider for HPE CSI Driver for Kubernetes
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
kadalu - A lightweight Persistent storage solution for Kubernetes / OpenShift / Nomad using GlusterFS in background. More information at https://kadalu.tech
longhorn - Cloud-Native distributed storage built on and for Kubernetes
zfs-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend ZFS data storage stack.
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
zfsmanager - ZFS administration tool for Webmin
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
Hardware - The devices I have, what runs on them, their configurations, issues, solutions, and associated projects
k3s - Lightweight Kubernetes
Portainer - Making Docker and Kubernetes management easy.