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

Hi,
I got a weird behavior when upgrade AWS ManagedNodeGroup with Pulumi. Based on the documentation, when upgrade, a new node group is created. My nodegroup contains a single node only, and I believe exactly one new node should be created. But actually, 6-7 new nodes is created, then each is removed later. It makes the upgrade process take long time (20-30 minutes for a node group of 1 node).

Is it normal behavior or something wrong with my configuration ?

Reference: <https://github.com/pulumi/pulumi-eks/blob/master/docs/eks-v3-migration.md#gracefully-upgrading-node-groups>

This is a known issue with EKS managed node groups: <https://github.com/aws/containers-roadmap/issues/1560>

I'm a bit surprised though that it creates 6-7 nodes if your node group has a size of 1. Do you mind sharing your config?