Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
s
some-continent-1577
04/12/2022, 1:12 PMHi all, I came across the fact that in python pulumi_aws, pulumi_aws.eks.NodeGroupScalingConfigArgs has desired_size as required. Does this make sense somehow? I thought it should be optional; for an autoscaling eks cluster, I’d like some way to be able to update the other scaling configs without changing desired count.
(I’m using pulumi_aws v4.26.0), but looks like this is still required in the latest version - https://www.pulumi.com/registry/packages/aws/api-docs/eks/nodegroup/#desired_size_python
The issue here is that if I want to update e.g. the max_size of my autoscaling cluster (or just refresh the stack for whatever reason), I need to update the pulumi script with the current desired sizes too or else pulumi will undo whatever autoscaling changes have been made — this is pretty terrible for maintainability
Sounds like ignoreChanges could help here, but NodeGroupScalingConfigArgs doesn’t accept ResourceOptions - https://github.com/pulumi/docs/issues/4721
It seems I should be able to pass opts=ResourceOptions(ignore_changes=[“scalingConfig.desiredSize”]) to the pulumi_eks.ManagedNodeGroup, but somehow that’s still showing desired_size being updated when I do pulumi preview