Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-452

[tech-preview] Proper state reporting when the MCO changes state


    • MCO state reporting
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-845 - [Tech Preview] Proper MCO State Reporting
    • OCPSTRAT-845[Tech Preview] Proper MCO State Reporting
    • 0% To Do, 14% In Progress, 86% Done
    • 0
    • 0

      The MCO should properly report its state in a way that's consistent and able to be understood by customers, troubleshooters, and maintainers alike. 

      For this epic, "state" means "what is the MCO doing?" – so the goal here is to try to make sure that it's always known what the MCO is doing. 

      This includes: 

      • Conditions
      • Some Logging 
      • Possibly Some Events 

      While this probably crosses a little bit into the "status" portion of certain MCO objects, as some state is definitely recorded there, this probably shouldn't turn into a "better status reporting" epic.  I'm interpreting "status" to mean "how is it going" so status is maybe a "detail attached to a state". 


      Exploration here: https://docs.google.com/document/d/1j6Qea98aVP12kzmPbR_3Y-3-meJQBf0_K6HxZOkzbNk/edit?usp=sharing




            cdoern@redhat.com Charles Doern
            jkyros@redhat.com John Kyros
            Charles Doern, Sinny Kumari
            Rio Liu Rio Liu
            0 Vote for this issue
            14 Start watching this issue