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

Was it just a matter of not waiting long enough?  Or did it legitimately fail to get healthy?

The timeout can be configured with `customTimeouts` - but it is possible that we don't yet thread through control of the timeouts on the ASG here from the `eks.Cluster` component.  We are working on a general mechanism to allow this sort of customization in <https://github.com/pulumi/pulumi/issues/2068>.

Ultimately it succeeded on the AWS side, but I haven't checked what was not run after that section and if I can re-run the stack without any problems.

I love the idea of an "escape hatch" as there's always something that gets missed or dropped when layering on abstractions