What

This Jira is a tracking Jira for general improvements and open discussion on:

• system names - some CRDs allow for specifying system name (backend CR) - some don't. It would be nice to find a common ground
• usage rules - use rules can be set at the product and tenant levels. Can't be set via CRDs - how much do we want these to be configurable via CRDs
  • at product level these enable following:
    • default plan
    • app requirements
    • app plans config
    • alerts
  • at tenant level:
    • User Account Management Zone
    • signup
    • users
    • search
    • advanced plans
    • service plans

• status reporting - ideally, we should have same possible status reporting across all CRDs. Proposal is "ready or not" - which is a single state of CR where a CR is either ready or not. Then based on the error type when going into not ready state, the reconciler would either be queued up again or "switched off" unti further changes. For example: in case of creating account, we want the reconciler to repeat reconciliation - this is due to the CR needing an admin user CR, since we don't know when is that going to be created, we need a continous reconcile loop. On the other hand, if a CR fails validation, there's no point in reconciling over and over again since any required changes will re-trigger a new reconiler regardless.
  Analysis of error types and differences between CRDs statuses: https://miro.com/app/board/uXjVMoMWDRE=/?share_link_id=977717577752

• reconiler flows - proposed flow in: https://github.com/3scale/3scale-operator/pull/874