This message was deleted.
# aws
s
This message was deleted.
b
you can
ignoreChanges
to the AMI
p
So I guess I can use 1 stack with 2 node pools and when the updtae happens ignoreChanges on one pool, update the other and then stop ignoring them and updating the secon
d
b
what are you ultimately trying to achieve?
p
A resilient cluster which can survive updates to the cloudformation stack which include things like changing the ami- or the node types. i.e. something where I can update the pulumi/eks module for different node pools at different times. Thus ensuring I can make such updates without downtime for my essential services.