Description

Daemonset deployment testing revealed that the timestamp update of the KataConfig status can cause the controller to enter a tight reconcile loop.

Steps to reproduce

1. Install OSC 1.10.3
2. Enable daemonset deployment in the feature gate CM
3. Create kataconfig
4. Wait for kata to be fully deployed
5. Run oc logs -n openshift-sandboxed-containers-operator deployments/controller-manager -f

Expected result

Log should be still.

Actual result

A new reconcile is logged every few seconds.

Impact

Waste resources

Env

Additional helpful info

Analysis highlighted that this issue could potentially happen with the MCO depoyment as well by just adding a time.Sleep.