The node controller reads the current nodestatuses from a lister, then makes builds an apply configuration that includes all fields of each nodestatus entry based on the value observed from the lister. If another controller (especially the installer controller) has written to a nodestatus, but that write was not reflected in the lister before the node controller observes it, the node controller's apply request will effectively revert to the last status its lister observed.

Before 4.18, these control loops were update-based and would receive 409 responses instead of successfully stomping unobserved writes.

    1.
    2.
    3.