Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
e
early-monitor-45939
07/01/2021, 11:03 PMHi, I wanted to create a ManagedNodeGroup on AWS EKS, but when I pass 0 for desiredSize, 0 for minSize and 1 for maxSize
pulumi upl
little-cartoon-10569
07/01/2021, 11:17 PMI don't know the entire answer, but I do know that 0 for minSize isn't allowed. According to the AWS SDK:
minSize — (Integer)
The minimum number of nodes that the managed node group can scale in to. This number must be greater than zero.
Maybe the rest of the values are undefined on return if minSize is 0?
e
early-monitor-45939
07/01/2021, 11:24 PMhttps://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
l
little-cartoon-10569
07/01/2021, 11:49 PMIt'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...
Since that's when the release happened.
You need pulumi/aws 4.9.0 (22 June) or greater, do you have that?
e
early-monitor-45939
07/02/2021, 5:49 PMHi, 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.
Should I open an issue on Github?
Update:
eksctl