flatcar-linux-update-operator
flatcar-linux-update-operator copied to clipboard
Documents labels and lifecycle of update
Original issue: https://github.com/coreos/container-linux-update-operator/issues/19
We should ensure that we have good documentation about existing behaviors.
Not sure if 100% accurate, hence the comment and not the PR, but from what I understand from the code, flow looks like on the image below. Note, that some steps are skipped (selecting nodes which can be rebooted, draining the node etc.)

And obligatory meme:

Slightly different version with highlighted stages I was able to identify:
