2 ms·
A little confused, you say you don't want to disrupt the containers, but https://github.com/bottlerocket-os/bottlerocket#updates https://github.com/bottlerocket
by Bedon292 6y ago
A little confused, you say you don't want to disrupt the containers, but https://github.com/bottlerocket-os/bottlerocket#updates https://github.com/bottlerocket-os/bottlerocket#updates seems to indicate you still have to reboot for the update to take hold?
- creztoe 6y agoI agree with the confusion. There is the ability to rollout updates in a "wave"[1], but I'm not sure how this is better than a simple rollout strategy in kubernetes since a reboot of the node seems inevitable. [1] https://github.com/bottlerocket-os/bottlerocket/tree/develop/sources/updater#update-wave https://github.com/bottlerocket-os/bottlerocket/tree/develop...