No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

some people are doing it successfully in production, so the question is more do you want to manage the service yourself or not

Yeah that much is obvious. I'm interested in hearing about folks specific in-cluster DB war stories.

In a previous life, I fighted with redis sentinel setup (<https://redis.io/docs/management/sentinel/#sentinel-as-a-distributed-system>) over k8s, I was never be able to make the failover working properly

before I worked at Pulumi, I ran a large Kubernetes platform that used Vitess on Kubernetes. I never experienced any data loss, but the management overhead pushed us to use RDS instead and we never looked back. What cloud provider are you using <@U05J4JC7J6L>?

my recommendation is that if you go down this path, don’t use just a standard k8s deployment and hope for the best. Use a Kubernetes native database with an operator like vitess

<@UCWG26BH7> I’m using digitalocean. A kubernetes native database aye? Does postgresql qualify as one?

Not on its own, if you use the postgres operator or something like <https://cloudnative-pg.io/>

but honestlu I’d just use the managed digitalocean service, it’ll save you a lot of time and effort

<@UCWG26BH7> do you remember a particular weird battle story you encountered when using one of these operators for a DB?