I think there’s a regression here with the EKS provider? https://github.com/pulumi/pulumi-eks/issues/88 An update to the ami on our nodes in our non production cluster just caused all the nodes to roll. Thankfully I caught this in non-prod but super scary!! You can see the replace strategy on imageId in the plan for our production cluster here:

Previewing update (base.prod):
     Type                                     Name                                               Plan        Info
     pulumi:pulumi:Stack                      yd-base-base.prod
     └─ yd:eks:Cluster                        yd-eks
        └─ eks:index:Cluster                  yd-eks
           ├─ eks:index:NodeGroup             yd-eks-nodes-datomic-http
 +-        │  ├─ aws:ec2:LaunchConfiguration  yd-eks-nodes-datomic-http-nodeLaunchConfiguration  replace     [diff: ~imageId]
 ~         │  └─ aws:cloudformation:Stack     yd-eks-nodes-datomic-http-nodes                    update      [diff: ~templateBody]
           └─ eks:index:NodeGroup             yd-eks-nodes-default
 +-           ├─ aws:ec2:LaunchConfiguration  yd-eks-nodes-default-nodeLaunchConfiguration       replace     [diff: ~imageId]
 ~            └─ aws:cloudformation:Stack     yd-eks-nodes-default-nodes                         update      [diff: ~templateBody]

@swift-intern-18856 are you hardcoding your AMI or allowing it to pull the latest? this doesn't look like a regression, it's expected behaviour as far as I'm aware

am i understanding the resolution of the linked ticket incorrectly?

the linked issue is from 2019, I believe we changed the behaviour since then again because otherwise it becomes difficult to update a launchconfiguration ami id

okay yeah, not hard to specify

@swift-intern-18856 btw a complete node roll is normal and healthy in kubernetes. If you can't roll you got problems that will bite you eventually. Unplanned version upgrades... not so much. I can see why people want this but it seems a not grow defailt