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

Untitled.ts

Code snippet regarding my postgres setup into K8s

I feel like I'm missing something obvious and when I see it I'm going to bang my head to a wall

I'm not trying to change into `Deployment` instead of `Statefulset` and changed my `PersistentVolumeClaim` to `ReadWriteMany` to allow using deployments. Also changed my `Service` to `NodePort`. Let's see if this has any effect on this...

It shouldn't. If it does help then I'd say this is a bug in Pulumi. But right now I would be thinking it's more about an issue in my code :slightly_smiling_face:

Eh... Wat. It tries to say "replace" for the statefulset even though it is not there anymore. Did `pulumi refresh`. It's not in the code or at the cluster at this point but apparently it is in Pulumi state

Right, had to go back to `StatefulSet`, but again it gets stuck

I think I'm facing this one <https://github.com/pulumi/pulumi-kubernetes/issues/1514>

Oh god... Found it. I had forgotten to add namespace to my Service declaration... No wonder it didn't find any pods :joy:

Like I guessed, this was something very stupid. Sorry to bother you!