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 I may have a hunch this is due to me creating a managed node group before the configmap

Which then AWS under the hood creates that configmap for me. Whilst the `pulumi-eks` creates the configmap before the managed node groups. Going to test that logic out

That rationale tracks, the issue is likely the name conflict, not the language SDK.

Ok so that is exactly what happened. you need to create the configmap before any managed node groups else it creates it automatically