This message was deleted.
# generals
sparse-intern-71089
12/09/2021, 5:53 PMThis message was deleted.
b
billowy-army-68599
12/09/2021, 5:54 PM
@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
s
swift-intern-18856
12/09/2021, 5:54 PMam i understanding the resolution of the linked ticket incorrectly?
swift-intern-18856
12/09/2021, 5:55 PMit seems to suggest image id will be ignored after the cluster is created
swift-intern-18856
12/09/2021, 5:56 PMb
billowy-army-68599
12/09/2021, 5:57 PM
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
billowy-army-68599
12/09/2021, 5:58 PM
billowy-army-68599
12/09/2021, 5:59 PM
in any case, it's relatively easy to fix by specifying an amiId
❤️ 1
s
swift-intern-18856
12/09/2021, 5:59 PMokay yeah, not hard to specify
swift-intern-18856
12/09/2021, 6:00 PMa little surprising that that’s the default behavior, kinda agree with the original ticket that’s a huge foot gun
swift-intern-18856
12/09/2021, 6:00 PMthanks for your help!
r
rich-businessperson-35436
12/10/2021, 12:21 PM@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
2 Views