VEverdverm·Dec 14, 2023
If you are on k8s, the Zalando operator is an excellent choice: https://github.com/zalando/postgres-operator
In Open and portable Postgres-as-a-service. Also available on Hetznerzalando
postgres-operator
Go2017–2025
zalando / postgres-operator
postgres-operator
Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
21Distinct people
25Mentions
1Explicit recommenders
5.3KGitHub stars
What to know before exploring
What it is
Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
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…
rektide used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year25 dated mentions
Observed mentions: 2017-10-11 06:23:42 UTC to 2025-12-20 17:33:36 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesyes, 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
In CloudNativePG – Postgres Operator for KubernetesI personally like the Zalando operator better, you can add databases and users by updating the CRD, feature parity between the two on HA is pretty good
https://github.com/zalando/postgres-operator
In How Modern SQL Databases Are Changing Web Development: Part 1one 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. (it also comes with a haproxy config to have a single leader connection)
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)
In Why PostgreSQL High Availability Matters and How to Achieve ItAs far as I understand Zalando does this. They have their own PostgreSQL operator https://github.com/zalando/postgres-operator.
In MRSK: Deploy web apps anywhereAnd 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.
In Databases on Kubernetes is fundamentally same as a database on a VMIn Kubernetes a service call end an operator watches for CRD specifying databases to be created and manages upgrade and backs for those databases.
https://github.com/zalando/postgres-operator
In Features I'd Like in PostgreSQL