OSDOCS 17238 Update MCO to reflect API changes made for Status Reporting

Author: Michael Burke

modules/checking-mco-node-status.adoc

@@ -15,9 +15,23 @@ The node update process consists of the following phases and subphases that are
 
 * *Update Prepared*. The MCO stops the configuration drift monitoring process and verifies that the newly-created machine config can be applied to a node.
 * *Update Executed*. The MCO cordons and drains the node and applies the new machine config to the node files and operating system, as needed. It contains the following sub-phases:
-** *Cordoned*
-** *Drained*
-** *AppliedFilesAndOS*
+** *Cordoned*. The MCO cordoned the node.
+** *Drained*. The MCO drained the node.
+** *AppliedFilesAndOS*. The MCO has updated the node files and operating system.
+** *AppliedFiles*. The MCO has updated the node files.
+** *AppliedOSImage*. The MCO has updated the operating system.
++
+In order to see *AppliedFiles* and *AppliedOSImage* in the output, you must enable the `TechPreviewNoUpgrade` feature set on the cluster. These conditions replace *AppliedFilesAndOS*. For more information, see "Enabling features using feature gates".
++
+[NOTE]
+====
+Enabling the `TechPreviewNoUpgrade` feature set cannot be undone and prevents minor version updates. These feature sets are not recommended on production clusters.
+====
++
+--
+:FeatureName: The `AppliedFiles` and `AppliedOSImage` condition 
+include::snippets/technology-preview.adoc[]
+--
 * *PinnedImageSetsProgressing* The MCO is performing the steps needed to pin and pre-load container images. 
 * *PinnedImageSetsDegraded* The pinned image process failed. You can view the reason for the failure by using the `oc describe machineconfignode` command, as described later in this section.
 * *NodeDegraded* The node update failed. You can view the reason for the failure by using the `oc describe machineconfignode` command, as described later in this section.