This message was deleted.

sparse-intern-71089

04/12/2022, 1:12 PM

This message was deleted.

some-continent-1577

04/12/2022, 1:12 PM

(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

some-continent-1577

04/12/2022, 1:23 PM

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

some-continent-1577

04/12/2022, 1:37 PM

Sounds like ignoreChanges could help here, but NodeGroupScalingConfigArgs doesn’t accept ResourceOptions - https://github.com/pulumi/docs/issues/4721

some-continent-1577

04/12/2022, 1:47 PM

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

16 Views

Open in Slack

Previous Next

Pulumi Community

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.