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

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

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

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.

awesome, by deleting the resources in the cluster and doing `pulumi refresh` you achieved a very similar result! glad it got sorted

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

yep! you can set these globally with `pulumi config set kubernetes:xxx`

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

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