This message was deleted.
# awss
sparse-intern-71089
07/06/2022, 4:06 PMThis message was deleted.
b
billowy-army-68599
07/06/2022, 4:07 PM
you can
ignoreChangesbillowy-army-68599
07/06/2022, 4:07 PM
p
polite-napkin-90098
07/06/2022, 4:08 PMSo 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
polite-napkin-90098
07/06/2022, 4:08 PMd
b
billowy-army-68599
07/06/2022, 4:12 PM
what are you ultimately trying to achieve?
p
polite-napkin-90098
07/07/2022, 5:00 PMA 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.
10 Views