[pwmtr]

At another thread in this page, I wrote more about this, but in summary; we also like k8s-based managed Postgres solutions. They are quite useful if you are running Postgres for yourself. In managed Postgres services offered by hyperscalers or companies like Crunchy though, it is not used very commonly.

[tehlike]

I always assumed crunchy was using their own operator for their managed offering. Is that not the case?

https://github.com/CrunchyData/postgres-operator

[pwmtr]

They have a Ruby control plane; https://www.crunchydata.com/blog/crunchy-bridges-ruby-backen...

[JohnMakin]

> it is not used very commonly.

Is this a problem of multi-tenancy in k8s specifically or something else?

[pwmtr]

At k8s, isolation is at the container level, thus properly isolating (for security purposes) system calls is quite difficult. This wouldn't be a concern if you are running Postgres for yourself.

Also for us, one reason was operational simplicity. You can write a control plane for managed Postgres in 20K lines of code, including unit tests. This way, if anything breaks at scale, you can quickly figure out the issue without having to dive into dependencies.