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

There are 2 methods to create node groups and it depends on whether you want to self-manage it [1], or have AWS manage it for you [2].

The trade-offs between the two that can be better understood by [3] and [4].

1. Example - Self-managed: <https://github.com/pulumi/pulumi-eks/tree/master/nodejs/eks/examples/nodegroup>
2. Example - AWS managed: <https://github.com/pulumi/pulumi-eks/tree/master/nodejs/eks/examples/managed-nodegroups>
3. <https://github.com/aws/containers-roadmap/issues/585>
4. <https://eksctl.io/usage/eks-managed-nodegroups#feature-parity-with-unmanaged-nodegroups>

&gt;  Which is the recommended way?
It depends on what level of control you want. Per the trade offs, if you need node tainting and other configurable properties on nodes to use for scheduling predicates, going the self-managed route is your best bet until [3] makes progress.

&gt;  Why when using `new NodeGroup()` that my pods in that nodegroup can’t resolve DNS?
Hmm, I haven’t heard of that one before. What does your set up look like? Can you try the self-managed node group example and see if that works?