This message was deleted.

But then you'll get an inconsistent state, no? Since resources can't run without a cluster.

Yes, but since the cluster was deleted, cant we assume that the resource was deleted ?

Not without destroying the resources first.

thank you.

That all depends on your use case as well. I can even envision some non-prod scenarios where you wouldn't even care about the state at all.

Yes, In my case I not care about the state after that step

I see, so you don't want to spend time destroying the resources individually

Yes. And some resource can be timed out, having to rerun pulumi destroy.

I'm sorry I can't help you with that. If I were in your shoes maybe I would just run an API call against whichever service you're using, bypassing Pulumi, but I don't know if that fits your use case or not.

Thank you.

You can create one stack for k8s cluster creation and another stack for k8s resource creation. then you can destroy the k8s cluster creation stack which only destroys the cluster. after that you only need to cleanup the now orphaned states from the k8s resource stack. this can be done by exporting the stack, deleting all resources from the exported file and reimporting the cleaned stack. i'm sure this can be automated using some bash/sed magic.