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

Posting it here to see if others are facing promise leaks with pulumi-eks providers v3 onwards

• Our current pulumi stacks that have EKS clusters use the following providers
    ◦ *`"@pulumi/aws": "^6.83.0"`* and *`"@pulumi/eks": "^2.7.9",`*
• updating these to AWSv7 and EKSv3 or EKSv4 is causing promise leaks
Over the past few months I have tried various things but these promise leaks are deep down into the abstractions in the pulumi SDK and the Pulumi team have also not been able to figure it out (<https://github.com/pulumi/pulumi-eks/issues/1826>, <https://github.com/pulumi/pulumi-eks/issues/1466>, <https://github.com/pulumi/pulumi/issues/18705>)

While just upgrading to AWSv7 provider we have issues in the stacks as they depend on EKSv3 and hence again we start seeing leaks. Also note any workaround suggest by pulumi team is also not possible so far as its causing the resources to be deleted

I was able to create a new stack and eks cluster with AWSv7 and EKSv4 providers without promise leaks, however as soon as I create any kubernetes resources via pulumi that references the cluster (even just a namespace) we see promise leaks.