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

Hi- apologies for the tardy response. Unfortunately, I think the github issue you linked :point_up: details the issue you are facing. I do not know of a workaround off the top of my head, but I have asked our internal team for some additional support, including potential workarounds.

Also, if you don't mind giving the github issue a :thumbsup: , this will help our team prioritize the backlog of work. Thanks!

I see, thank you for the confirmation :thumbsup:

<@U037Y6YB153> After doing some thinking/digging, I think you might be able to make use of the `skipAwait` annotation in Pulumi Kubernetes as a workaround here.

<https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/>

Thanks <@U025WUAUECC>, tested this out and it works :thumbsup: