If the operator can't install one of the components, it goes into a tight loop with no back-off. The easiest way to reproduce this is to enable kiali in the SMCP when the kiali operator is not installed.

The operator keeps trying to create the kiali resource, which fails. The operator then updates the SMCP status. Even though the SMCP.status.components conditions don't change (i.e. the components that were successfully installed have the condition status set to True and the component that wasn't installed has it set to False), the lastTransitionTime field is updated on all components that were installed successfully. Since the condition's status hasn't changed, the lastTransitionTime shouldn't either.

Because the SMCP status is updated, this causes the watch event to trigger another reconciliation, bypassing the back-off mechanism and causing the tight loop.