postgres-operator
dbhub.io
Our great sponsors
postgres-operator | dbhub.io | |
---|---|---|
33 | 8 | |
3,719 | 356 | |
1.9% | 1.7% | |
9.0 | 9.5 | |
7 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | GNU Affero General Public License v3.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
- 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?
dbhub.io
-
A SQLite extension that brings column-oriented tables to SQLite
We have a spread of different GitHub Actions based workflows that do stuff whenever a PR is proposed or merged:
https://github.com/sqlitebrowser/sqlitebrowser/tree/master/....
Most of those are oriented around building packages for various OS's (Linux, macOS, Windows) so people can try the latest code.
While there are some tests, they're more like extremely basic sanity tests and don't rely on Docker.
Those tests rely on whichever version of SQLite was downloaded and compiled into the GUI (as per above code snippet).
---
That being said, that's for the client side GUI application. There's a server side of things too (https://github.com/sqlitebrowser/dbhub.io -> dbhub.io) that does use docker for it's automated tests:
https://github.com/sqlitebrowser/dbhub.io/tree/master/.githu...
Those are integration tests though (eg "make sure we didn't bust communication with our cli", "make sure our go library still works 100% with the server"), and a reasonably decent set of End to End (E2E) tests of the web interface using Cypress.
---
Does that help? :)
-
Systemd auto-restarts of units can hide problems from you
> I now have some Go websites running for a long time with daily Systemd restarts.
Are the restarts needed because there's malicious over-size content being sent to it, trying to exhaust the server resources?
If so, then "http.MaxBytesReader" might be helpful:
https://github.com/sqlitebrowser/dbhub.io/blob/5c9e1ab1cfe0f...
-
How to Check 2 SQL Tables Are the Same
Not sure if Go code is your kind of thing, but if it is my colleague wrote a SQLite "diff" capability for our online hosting operation:
https://github.com/sqlitebrowser/dbhub.io/blob/5c9e1ab1cfe0f...
The code there can also output a "merge" object out of the differences too, in order to merge the differences from one database object into another.
-
What would be the easiest way to make a database available online?
https://dbhub.io/ ?
- DBHub: SQLite Storage “In the Cloud”
-
User friendly GUI for OSX
It's open source, free, cross platform and frequently updated. You can also use https://dbhub.io as a way to backup and share your databases.
-
Made a Python library for accessing and using SQLite databases on DBHub.io
I just finished my project 'pydbhub ' for accessing and using SQLite databases on DBHub.io.
- DBHub – SQLite Storage “In the Cloud”
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.
sqlitebrowser - Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
nocodb - 🔥 🔥 🔥 Open Source Airtable Alternative
longhorn - Cloud-Native distributed storage built on and for Kubernetes
pydbhub - A Python library for accessing and using SQLite databases on DBHub.io
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
datasette - An open source multi-tool for exploring and publishing data
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
Sequel-Ace - MySQL/MariaDB database management for macOS
k3s - Lightweight Kubernetes