Operator core update

[aslakknutsen]

Console Integration

• Move Session.Status.Refs.Resources to Conditions
• combine all RefStatus.'Status' into a signle Status Handle session.status.state #70
• Support components update on CRD for UI 'ready' wheel feat(operator): add podStatus ui wheel to component #875

  status:
   readiness:
      components:
        pending: []
        ready:
          - grafana
          - istio-discovery
          - istio-egress
          - istio-ingress
          - kiali
          - mesh-config
          - prometheus
          - telemetry-common
          - tracing
        unready: []
  

Reporting

• add multi error to all mutators Evaluate switching to emperror #797
• Add a 'realtime' status update type callback
• write state/failure to the Event API

Target project Validation

• ( "DryRun" Conditions to show full expected state on first run through, for then to become 'true' over time) Populate the Conditions with the Locator status before Modification #864

Refactor/Debt

• rework locators/mutators/revertors into a 'Rule/Condition' type structure
• combine mutators and revertors
• Single location for convertion between external/internal objects
• ( Reconcile per Condition )
• move Session locator state to Context object
• Don't rely on Status for state storage, tag objects with Labels/annotations (this was under the assumption that status was an open field anyone could edit, but it's a separate path and under rbac so less likely). An error cause could fail to update status but after the changes have occured leaving us with an unknown/leaky sate.

Done

• Add reason/cause message to status - Add reason/cause message to status #766
• Add timestamp to status - Add timestamp to status #765
• support Kind as part of ref name to be specific between Deployment and DeploymentConfig Support Kind as part of RefName to be specific between Deployment and DeploymentConfig #783
• add custom resource view for cli Add custom resource view for cli #782
• separate between Action and Success on RefStatus (Modified Failed) Separate between Action and Success on RefStatus #781

[aslakknutsen]

Ref Update impl strategy

• Ref.Hash() consistent to be used as a version number
• add support for version/generation in reference.Add|GetLabel
• Locators would need to check if there are existing Resources, and if they match or not the Hash
  • same as we do on 'Delete', but check if hash match
  • Depending on the Locator; Either do nothing, or create two LocatorStatus given action aka Delete and Create
• LocatorStore(or up to the Modificator), need to Sort results in 'delete/revert' before 'create/modify'

Ref.Deleted

• find all effected Resources

Ref.NotDeleted

• find all Resources that should be effected

ref.NotDeleted && !Hash

• find all effected Resources
• find all Resources that should be effected