I noticed the following behaviour during manual testing of an overlay setting:

I got the overlay syntax wrong on first try, which caused the operator to enter a reconcilliation error/rollback loop.

This had the additional undesirable effect that it prevented the manual fixing of the custom resource due to the operator constantly updating the custom resource with a new status.

What I did to mitigate this is

kubectl -n <namespace> annotate central <CR name> stackrox.io/pause-reconcile="true"

This then allowed me to fix the problem in the CR, afterwards I unpaused the reconcilliation of this CR.

It's a bad UX. The operator should notice such a problem and stop updating the CR continuously.{}{}