Description of problem: Nodelink controller never rests. With a very small amount of nodes and machines, it is constantly emitting dozens of logs ever second, forever. We should figure out why it's burning up some much CPU time and possibly have it trigger actions on node/machine update events.
This is by design atm. It's triggering actions on node/machine update events which happen very frequently due to node heartbeating status updates. Once we make machines "fire and forget" we can let the nodelink controller to stop watching nodes and only watch machines which will reduce the reconciliation cadence
I'm closing this for now as per https://bugzilla.redhat.com/show_bug.cgi?id=1732609#c1. In the near future we'll hopefylly drop the node link controller completekly, move the linking logic in to the machine controller and probably slighty reducing its resync period.