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’m also in the process of implementing managed node groups.  Initially I tried using the `eks.createManagedNodeGroup` function, but found it was exhibiting weird behavior.  If you update to the latest version of `@pulumi/eks` you’ll find that they’ve added the `ManagedNodeGroup` class.  A lot of weird behavior I was seeing was resolved after swapping the function for the updated class.  Good luck.

Hi <@U0105GGB28G>, did you manage to make that work? If so can you share your experience? I'm trying to taint my GPU node group.

Hi <@U01QUKUMRC5>, unfortunately not. If you are successful, please let me know :slightly_smiling_face:

<@U0105GGB28G> I noticed that I was using the `aws.eks.NodeGroup` instead of the `eks.NodeGroup` that <@U01EQUVQ9F1> mentioned above. I haven't tried yet since I have some other issues to tackle before. I found <https://www.pulumi.com/docs/guides/crosswalk/kubernetes/worker-nodes/#pod-scheduling|this> on pulumi docs. The plan is to add new nodegroups using the correct class and drain the old ones.

it's just super confusing that there's two classes. In my case, someone else wrote the cluster and I was inspecting the code for `aws.eks.NodeGroup` trying to find a solution instead of searching the docs.