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

Were the StatefulSet and associated PVCs created using Pulumi?

So what happens when you run `pulumi destroy`?

I guess it might be a specific case because I have a set of hostName (therefore `storageClassName: "manual"`) PersistentVolumes that then get bound by StatefulSet

so pulumi destroy hangs on trying to remove PVs but kubernetes won't remove them until PVCs exist and PVCs are not deleted due to <https://github.com/pulumi/pulumi-kubernetes/issues/218>

if I run `kubectl delete pvc --all` in second terminal it continues and cleans up everything correctly

Gotcha. Yes, I’d agree with your assessment that this appears to be related to `pulumi-kubernetes#218`. I’m not aware of a workaround, but I’ll ask some engineers internally just in case.

there is an obvious workaround related to manual removal of these PVCs so not a complete blocker :wink:

not perfect from the perspective of automating such stuff though :confused:

Yep, I get it. I’ve asked internally, and I’ll respond here if I get any suggestions. (Or one of our engineers will chime in; a lot of them frequent this Slack community on a regular basis.)

One suggestion to consider: you could use the `pulumi-command` provider to automate some of the cleanup process.

for anyone wondering about that - apparently dropping the whole namespace also works so separating the workload into it's own namespace is one way out too