Note the "except if you have a very good reason" caveat.

I think this is a good ops team mantra. PostgreSQL unless you have a very good reason otherwise, and k8s unless you have a very good reason otherwise.

Decisions like this allow for economies of scale with tooling, monitoring/observability, etc.

Saying no to snowflakes is an important part of having a good ops team.

Guess it depends on who is defining “very”.

A persistent connection is antithetical to the design of kubernetes.

Persistent storage is hard to get right in kubernetes and puts a lot of pressure on the cluster being perfect, which is something a good ops team will tell you is hard.

If your application is stateless http services then kubernetes is great, but there are common things that don’t fit well, and forcing people into a solution which may require a complete rethinking is not very pragmatic.

Eh, for what it's worth they've deployed a couple of PostgreSQL instances for me using Kubernetes and it's worked exactly like I've wanted it to. But then again I've never had push those instances to breaking point either when it comes to IO or concurrency so who knows.