To release "Status Reporting" as General Availability (GA), we must determine which statuses are valuable to end customers. Therefore, we must evaluate the currently existing status conditions and understand what must be added to give a proper view into updates to our end users. Further, OnClusterLayering (OCL) updates are not well represented in the current implementation of MachineConfigNode (MCN), as OCL updates do not follow the same condition transitions as a traditional node update.

History:

• The original v1alpha1 API design for MCN contained 15 statuses, with 2 statuses specific to PinnedImageSets.
• Updates to the MCN API as part of MCO-1543 included:
  • Trimming down to 12 standard node update related statuses
  • Adding a node degraded condition
  • Keeping the 2 PIS related conditions
• There were some conversations on statuses for OCL as part of MCO-1535. More information on previous ideas can be found here.

Work for this spike:

This spike includes evaluating the existing statuses and determining what is needed to GA the Status Reporting feature. Some questions that might help in this evaluation include:

• Are the originally identified statuses valuable to end customers?
  • Descriptions/documentation should be clear
  • Status names, reasons, and messages should be clear
  • Statuses should not be so rare that they seem to never update/might lead customers to believe there are bugs
• What statuses are relevant for an OCL update? Should statuses be added to better support OCL? Are any existing statuses relevant to OCL that should be better utilized?
• Are there additional statuses that would provide greater debug-ability to customers? Would a repurposing of some statuses be helpful?

Done when:

• MCN statuses for Status Reporting GA are documented
  • This should include understanding statuses needed for OCL updates
• Statuses to populate for `oc get machineconfignode` and `oc get machineconfignode -o wide` are decided on and documented
• The description & story points for MCO-1675 are updated with information on the API updates needed as a result of this investigation work