Existing Ownership of sub resoucres [Edge Case]

[Boomatang]

Outline

With the merging of #350 and #393 the kuadrant operator will respect existing ownership values on the limitador and authorino CRs. Once an existing ownership is detected the kuadrant operator reports the error in the kuadrant operator but also stops reconciling the rest of the resources. The example here is if the limitador CR is owned by an existing controller none of the resources for authorino will be reconciled. And an infinite loop of trying to reconcile is created.

Cause

How I believe a user may get into this state is as follows. The user was using one of the sub components (authorino or limitador) as a standalone product before adopting kuadrant as a whole. For the sub component the user would make use of sub component CR. They would have needed to created their owner custom controller to manage that resource and added the owerReference to the CR metadata. Or the user uses a GitOps system to manage the resource and that GitOps system adds the owerReference to the resources.

My personal belief would be a GitOps system adding an owerReference being the most likely cause of this edge case.

Expected Behaviour

• Error report added to the Kuadrant CR status block - Currently happens
• Stopping reconcile of resource which has an existing owerReference set - Currently happens
• Continue to reconcile resources not related to the affected resource. - Does not happen.
• Exposing metric, alerts and events around the issue. - Unknown current state

[Boomatang]

Closing: The state of the world refactor fixed this issue.