DADasIch·Dec 30, 2018
https://github.com/zalando-incubator/postgres-operator supports point in time data recovery just fine and is used in production for 100s of databases at Zalando.
In KubeDB – Run production-grade databases easily on Kuberneteszalando
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, 6:01:08 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
3 sourcesA database would normally be deployed as a stateful set, with the data stored in a volume, created and maintained by a PVC (persistent volume claim). This mechanism ensures that in the case of your pod dying and getting recreated on a different volume, it would see the same data as before, with the PVC getting mounted on the same pod. This mechanism is still one of the weaker links in the Kubernetes chain, in my experience, as the PVC feature is implemented completely differently on each platform, and is prone to bugs (see https://github.com/kubernetes/kubernetes/issues/60101, from Kubernetes version 1.7 on Azure, for example). Kelsey Hightower himself mentioned in a tweet that he prefers hosted solutions for persistency, and Kubernetes for stateless applications. Also, you should have a look at operators for managing applications on Kube
Read the rest
rnetes, such as this one for PostgreSQL: https://github.com/zalando-incubator/postgres-operator.
Note that none of those things are impossible on kubernetes, k8s just doesn't offer them by default (which is good IMO).
There are projects that help you run databases in kubernetes and also make backups of many things hosted:
- Automatic CephFS for your cluster -> https://rook.io/docs/rook/master/
- Backups for cluster resources and volumes -> https://github.com/heptio/ark
- Spin up dynamic postgres clusters -> https://github.com/zalando-incubator/postgres-operator
Databases are just applications with different resource needs. Please stop pushing forward the notion that they can't be run in containers or container orchestration systems. Databases are just programs. If the substrate for running your containers doensn't reliably support flock or fsync or something your database needs, then maybe pick a better substrate that does -- contain
Read the rest
er runtimes these days and kubernetes don't stand in your way these days.