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

Would you mind raising an issue (with as much of the relevant code that you're able to share) in the GitHub repo for EKS? <https://github.com/pulumi/pulumi-eks>

Hi Scott, I am working on reproduction steps. I am trying to rule out that I've done something incorrect, but it does seem like this is a new issue. I'll put an issue together once I feel confident that it's not something incorrect on our end.

Fair. If we can help further, let me know.

it definitely appears that the fargate profiles are no longer created for the `default` or `kube-system` or perhaps there is a race condition. It's difficult to tell but from my testing, they're not in place which causes the `coredns` pods to be unschedulable and because there's no DNS, everything downstream (for us) fails without that.

just following up - I was able to work around the issues by creating a `waitFor` method that I could await and pass it the pulumi.Output&lt;T&gt; properties and now I get a consistent cluster up :+1:

This might still be worth opening an issue, if you have a few minutes to do so