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 don't know the entire answer, but I do know that 0 for minSize isn't allowed. According to the AWS SDK:
&gt; minSize — (Integer)
&gt; 
&gt; The minimum number of nodes that the managed node group can scale in to. This number must be greater than zero.

<https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/EKS.html>

Maybe the rest of the values are undefined on return if minSize is 0?

<https://docs.aws.amazon.com/eks/latest/APIReference/API_NodegroupScalingConfig.html> — according to this, 0 is allowed

was recently added to Terraform as well: <https://github.com/hashicorp/terraform-provider-aws/pull/19810>

It's allowed in the API and in the Go SDK, but not the JavaV2 SDK or the Javascript SDK. I guess it's not fully rolled-out everywhere, yet...

Does the terraform AWS provider cause the error? Maybe it gets picked up and rejected before it gets to AWS....

What I meant to say, was: what version of the Pulumi provider uses 3.46 (or newer) of the Terraform provider...

You need pulumi/aws 4.9.0 (22 June) or greater, do you have that?

Hi, I have tried creating a managed node group on AWS console with 0 minSize, 0 desiredSize and 1 as maxSize. AWS console allows it. So there’s definitely some issue on the Pulumi side. And yes, I am using the latest versions.

Like I said, seeing the “details” after “pulumi up” says 1 as minSize, 1 as maxSize and 2 as desiredSize (while I passed 0, 1 and 0 respectively). Pulumi seems to automatically change these values. So maybe there’s some error in the module that validates these arguments / replaces them by default values.

Update: `eksctl` supports the 0,0,1 use-case. So the error is definitely on the Pulumi side.