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

I think the conflict is with node_associate_public_ip_address

<@U02Q5CMLL3C> - did you ever figure this out? I’m seeing the exact same behavior in code that has been working for months, and now sporadically fails with the same errors you are seeing.

nope I did not, but I ended up creating my own managed node group and turned the default one off so it's no longer an issue for me.

I ended up using the same approach as <@U02Q5CMLL3C>. But it does not solve my problem where I need to have multiple Node Groups with distinct user data for each Group