postgres-operator
cloudflare-ingress-controller
DISCONTINUED
Our great sponsors
postgres-operator | cloudflare-ingress-controller | |
---|---|---|
33 | 1 | |
3,683 | 359 | |
1.9% | - | |
9.0 | 0.0 | |
6 days ago | about 1 year ago | |
Go | Go | |
Apache License 2.0 | 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
- Deploying Postgres on Kubernetes 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
- Do people use DBs as Pods?
- Is anyone using postgres on kubernetes?
-
Pgo: The Postgres operator from crunchy data
https://github.com/CrunchyData/postgres-operator/blob/master/LICENSE.md ???
cloudflare-ingress-controller
-
Ask HN: Does anyone use a fully Kubernetes-native stack at home/work?
I guess that would really depend on your setup. It would differ significantly if you’re doing virtualised nodes ontop of vmware/proxmox/qemi/etc, if you’re doing single node with storage, or if you’re doing something more exotic like raspberry pis with either one node with storage or external nas.
I have a couple of different setups (mostly for fun), which are pretty simple. Main things I use are a csi driver to allow me to use my trunas scale as storage (https://github.com/democratic-csi/democratic-csi), cloudflare’s argo tunnel to expose my clusters to the outside world (https://github.com/cloudflare/cloudflare-ingress-controller), an operator for managing external dns with cloudflare (https://github.com/kubernetes-sigs/external-dns/blob/master/...). Everything else is pretty much they way any other cluster would look.
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.
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
longhorn - Cloud-Native distributed storage built on and for Kubernetes
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
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
k3s - Lightweight Kubernetes
QuestDB - An open source time-series database for fast ingest and SQL queries
postgres - Unmodified Postgres with some useful plugins
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
percona-postgresql-operator - Percona Operator for PostgreSQL