setting statuses, and triggering reconciliation

[kristofgyuracz]

• scratch implementation
• api changes
• set tenant-> collector ref and notify controller on change
• triggering for relevant changes, disowning, and checking ownership before adopting tenants and subscriptions

[pepov]

Looks good to me overall, however we need to make sure we handle errors consistently.

Generally there is nothing wrong with returning an error and waiting for the next reconcile to fix it, but in this case we build a system where a misconfigured tenant/subscription should have the least possible effect on the other actors.
In this case if one subscription cannot properly be updated, then we get stuck and no configuration changes can be made anymore on the collector in general.

Update: we just want to handle subscription update errors in this special way to make sure a user updating their subscription won't be able to intentionally or accidentally block the system

[OverOrion]

Overall LGTM, two minor notes only.

[pepov]

looks great, a few nits I've added: put arm64 image build back and equality checks before collector/tenant updates