Separating the GAing of MachineConfigNode from the GAing of status reporting presents the opportunity to reevaluate the statuses tracked in the MCN conditions. The original V1alpha1 design contains 15 statuses, with 2 statuses specific to PinnedImageSets. This spike includes evaluating the statuses in terms of the following criteria:

• What are the minimum necessary statuses for GAing the MCN feature?
• What are the minimum necessary statuses for enabling the GAing of the PIS feature?
• Which statuses should be reevaluated for status reporting's GA (MCO-1506)?
• How can the MCN feature be made cleaner and easier to use (specifically in terms of the `oc get machineconfignode` and `oc get machineconfignode -o wide` columns)?
• Should the PIS statuses be included in the `oc get machineconfignode` and `oc get machineconfignode -o wide` columns?

Done when:

• Statuses to include in MCN GA efforts are decided on
• Statuses being included in MCN GA have clear documentation in the API, enhancement, and user facing documentation
• Decision has been made on which statuses should be included in `oc get machineconfignode -o wide` columns

Out of scope:

• Phases for OCL updates will be determined & added as part of the status reporting GA