This message was deleted.

sparse-intern-71089

08/04/2019, 7:09 AM

This message was deleted.

white-balloon-205

08/04/2019, 1:55 PM

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?

hundreds-portugal-17080

08/04/2019, 6:50 PM

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/

white-balloon-205

08/04/2019, 9:18 PM

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?

hundreds-portugal-17080

08/04/2019, 9:23 PM

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

white-balloon-205

08/04/2019, 9:34 PM

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.

hundreds-portugal-17080

08/04/2019, 9:35 PM

ok. thank you.

creamy-potato-29402

08/05/2019, 5:06 AM

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

31 Views

Open in Slack

Previous Next

Pulumi Community

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.