Should argocd have a sync timer?

[mhjacks]

I installed a new cluster on AWS, which by default does not have KVM support (so emulation needs to be set to "true", which it also isn't, by default).

I reconfigured my cluster to enable emulation (also adding the extra values file to the helm upgrade -i command line), but that did not help with bringing up image-builder-000. I deleted image-builder-000, hoping that it would be re-created, but it wasn't.

I subsequently learned that I had I triggered a re-sync with argo, it would have been re-built. The particular case I encountered would have (eventually) been fixed with an argo resync, once I had enabled emulation