This message was deleted.

sparse-intern-71089

09/02/2021, 3:55 PM

This message was deleted.

billowy-army-68599

09/02/2021, 4:04 PM

if I'm understanding correctly, you'll have to remove the offending resource from the state using

pulumi state delete

billowy-army-68599

09/02/2021, 4:04 PM

we do have open issues about better handling of this which I'll try dig out

👍 1

ripe-shampoo-80285

09/02/2021, 4:12 PM

I fixed it by manually delete the k8s resources using kubectl delete, followed by "pulumi refresh" and "pulumi up". I will try "pulumi state delete" the next time something similar happens.

billowy-army-68599

09/02/2021, 4:18 PM

awesome, by deleting the resources in the cluster and doing

pulumi refresh

you achieved a very similar result! glad it got sorted

ripe-shampoo-80285

09/02/2021, 4:31 PM

Thanks @billowy-army-68599. BTW, is there a way to specify default k8s cluster in the Pulumi.xxx.yaml configuration file much like we do with aws:profile?

billowy-army-68599

09/02/2021, 4:32 PM

yep! you can set these globally with

pulumi config set kubernetes:xxx

https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/#inputs

ripe-shampoo-80285

09/02/2021, 4:33 PM

Great, thanks!

bored-table-20691

09/02/2021, 6:10 PM

I also think you may have been able to do this with “delete before replace” for this particular resource, and then remove that later.

👍 1

4 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.