Description
There are multiple places in the code base where we follow this pattern of looping over nodes for file transfer (configmap_controller, controllerconfig_controller, regstry_controller), and all face the same issue: if any single VM flakes on file transfer, this is going to cause all other instances to go through the file transfer again. We should make this logic more resilient to avoid this potential issue.
Engineering Details
Might need to introduce a way to recognize that an instance is up to date in terms of file transfer in order to skip it, much like we do with the version annotation.
Acceptance Criteria
File transfer does not re-loop over all nodes in cluster if transfer to one fails.