Hacker News Reader

I don't keep up to date on all the k8s changes but a couple years ago wasnt the recommendation not to have your databases in k8s at all?

What has changed between now and then where putting postgres into k8s is an option?

Does the Postgres operator handle all the statefullness requirements and scheduling things that might be unique to pg?

View on HN

StatefulSets were added to handle things like this. It always seemed like an afterthought to me, appeasing people trying to run things that Kubernetes was never designed to handle.

At $BIG_CORP our executives became very excited about "The Cloud" and many teams were forced to migrate their applications over. Didn't matter if it was a proper 12 factor application or a monolithic vendor JAR that required 64GB of ram. You were punished for using VMs, so teams spent an inordinate amount of time shoving square pegs into round holes.

Reply on news.ycombinator.com