This message was deleted.

If the

pulumi destroy

completed successfully, these should have been removed. It's possible that if you tore down a cluster too fast after deleting the PVCs, that Kubernetes itself may have leaked the allocated volumes?

hmmm.. ok. thank you for your response.. i just tried and deleted all as you said... let me kind of observe this scenario more carefully next time.. in real world scenario, we don't want them to be deleted, how do we control it? I am not finding any parameters in https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/eks/

in real world scenario, we don't want them to be deleted, how do we control it

I don't exactly follow the scenario you have in mind here?

say, we create statefulset pods and preserve the data eventhough after he cluster goes down..

That is up to how you configure your PVs in Kubernetes. Pulumi will not destroy anything it does not manage, and the cloud-provider Volumes themselves are managed by Kubernetes not Pulumi.

ok. thank you.

depends where the pvc came from. stateful sets do not delete their underlying PVCs automatically.