This message was deleted.

this doesn't address your issue directly, but I use

NodeGroup

instead of

ManagedNodeGroup

. I don't know what the difference is between them, but

NodeGroup

does create an EKS managed node group and i think you'll avoid this issue you're getting if you use it instead

Thanks, that's helpful. Now that I read the docs again, I think I had misunderstood this part

To opt-in to using Managed Node Groups, the raw `aws.eks.NodeGroup` building block is available. However, we’ve enlightened the EKS package with the

eks.Cluster.createManagedNodeGroup

function to make it easier and to integrate with cluster provisioning.

I think by "enlightened" they just mean "you can do this from the

@pulumi/eks

package"

oh right, that makes sense. The

NodeGroup

I use is from

@pulumi/aws/eks

but

ManagedNodeGroup

is from

@pulumi/eks

The

@pulumi/eks

package is supposed to have a "better" API instead of a 1:1 match of the cloud provider API that

@pulumi/aws/eks

has. It's true to some extent, but if you are mix/matching the packages you can run into the issues you just saw here.

Yeah I am often a bit confused about which package I'm supposed to use, between

aws

and

eks

and

awsx

and then there's the "native" one... I will have a go with

aws.eks.NodeGroup

, thank you for your help!