helm-charts
postgres-operator
Our great sponsors
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- Onboard AI - Learn any GitHub repo in 59 seconds
- SaaSHub - Software Alternatives and Reviews
helm-charts | postgres-operator | |
---|---|---|
6 | 36 | |
583 | 3,658 | |
0.3% | 1.3% | |
0.0 | 0.0 | |
14 days ago | 8 days ago | |
Mustache | Go | |
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.
helm-charts
-
Connecting OpenSearch to Keycloak
Before we can authenticate OpenSearch against Keycloak, we'll need to install Keycloak. The following Ansible snippet demonstrates how to deploy Keycloak onto a Kubernetes cluster using the codecentric helm chart.
-
sso at home?
HA Keycloak on top of Kubernetes https://github.com/codecentric/helm-charts/tree/master/charts/keycloak I dropped the chart db in favor of https://github.com/zalando/postgres-operator
-
Homelab: Cluster Architecture
Having experienced the issue of identity management in past projects (I've literally published 5 web apps which became some iteration of user-profile applications), I found Keycloak to be of particular use when it comes to managing users and federating accounts. Keycloak is an open-sourced enterprise service which manages identity, authentication, authorization, and account federation which is part of the JBoss project and backed by RedHat. Since I wanted to use the Keycloak helm chart the Keycloak service runs using a Postgres backend.
postgres-operator
-
Run PostgreSQL. The Kubernetes Way
yes, precisely. It's UI part that's broken, which cannot list snapshots. Issue is here, no fix since 2020, sadly: https://github.com/zalando/postgres-operator/issues/937
- Deploying Postgres on Kubernetes in production
-
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)
-
[Kubernetes] Comment déployez-vous un cluster Postgres sur Kubernetes en 2022?
Zalando / Postgres-Operator
-
What are you using to run Postgres?
Somewhere between here and here i found out about that.
-
Databases on Kubernetes is fundamentally same as a database on a VM
And that repo you linked to has 1846 issues, 161 open. Which doesn't seem extraordinary based on my limited exposure to k8s.
Another example: https://github.com/zalando/postgres-operator/issues with 445 open issues. Why?
Maybe I'm wrong and this is all a good sign of progress, but my impression is that the entire k8s ecosystem is held together with reused duct tape.
-
Features I'd Like in PostgreSQL
In Kubernetes a service call end an operator watches for CRD specifying databases to be created and manages upgrade and backs for those databases.
-
Any self hostable postgres clustering, replication and fail over system?
You could fire-up `k3s` or `microk8s` or something of that ilk and run https://github.com/zalando/postgres-operator
-
Just Use Postgres for Everything
My favorite route right now is running a postgres operator on Kubernetes & letting it do all the work for me.
Zalando's operator use Patroni under the hood, to create a cluster over streaming replication. It also has Spilo, which orchestrates pg_basebackup or WAL-E for point-in-time backup. https://github.com/zalando/postgres-operator#postgresql-feat...
CrunchyData operator seems to have built their own streaming replication system coordinated by Raft. https://access.crunchydata.com/documentation/postgres-operat...
-
Best way for high-available database at home?
I don't have much experience with HA databases, so I can't really decide which way I should go. I found a postgres-operator to be run on a kubernetes cluster: https://github.com/zalando/postgres-operator. And a guide to setup postgres HA with patroni: https://arctype.com/blog/postgres-patroni/
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 - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
charts - Bitnami Helm Charts
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
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
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
postgres - Unmodified Postgres with some useful plugins
longhorn - Cloud-Native distributed storage built on and for Kubernetes
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
percona-postgresql-operator - Percona Operator for PostgreSQL
keycloak-theme-sample - Sample Keycloak Theme
helm-nifi - Helm Chart for Apache Nifi