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

Untitled.txt

Is this with the latest `@pulumi-kubernetes`?

I can’t replicate this because I was able to bypass it by destroying the resources and recreating them. The issue happened when I added the skipAwait annotation to a Service

Should be fixed by <https://github.com/pulumi/pulumi-kubernetes/pull/691> — fix will be in the next release

Thanks! I think I caused it by having a `true` value rather than `"true"` for the annotation.