11–20 of 28 posts
See https://www.reddit.com/r/PostgreSQL/comments/mqrsbn/kubegres...
So I can create 2 servers running kubegres, kill one and then all data should be intact? And no downtime?
Mind you, no clustered system can provide you zero downtime and zero data loss without essentially the same constraints. If you have an unplanned failure, there's going to be a blip somewhere. It's up to the rest of the system to recover from it gracefully.
When configuring any kind of cluster involving data (especially one that's supposed to recover automatically from faults), make sure you understand how it behaves and adjust for your application, because quite often the default configurations might accept some data loss in unplanned failover or conflict scenarios.
Is it logical for AWS to offer RDS over K8s?
Is it logical for AWS to offer RDS over K8s?
https://aws.amazon.com/blogs/opensource/aws-service-operator... https://github.com/aws-controllers-k8s/community
Since this is just a PR announcement by a third-party posted on an official PostgreSQL page: what is the difference between this and established PostgreSQL operators by Zalando and CrunchyData?
I was wondering this too and found: https://www.kubegres.io/#kubegres_compared It seems like the big difference is that it uses the standard PostgreSQL Docker images and doesn't bundle together as many things as Zalando or Crunchy Data. They'd likely argue that makes it easier to learn and a smaller surface area for attacks or things to go wrong. Crunchy Data includes lots of add-ons like pgBouncer, pgAdmin 4, pgMoni…
Where I can read how modern k8s deals with persistent storage? It looks like after pg cluster shutdown you lose all data.
I use https://rook.io/ to set storage up usually, they have a bunch of different options and good documentation.
1) Applications reconnecting to the new Postgres master and retrying queries
2) Persistent storage available in multiple AZs or regions for your Postgres pods (impossible on AWS for example)