Merge pull request #97345 from mburke5678/mco-ocl-418-backport-pt-2

MCO Backport OCL to 4.18 part II

Author: mburke5678

machine_configuration/mco-coreos-layering.adoc

@@ -30,11 +30,6 @@ As soon as you apply the custom layered image to your cluster, you effectively _
 There are two methods for deploying a custom layered image onto your nodes:
 
 On-cluster layering:: With xref:../machine_configuration/mco-coreos-layering.adoc#coreos-layering-configuring-on_mco-coreos-layering[on-cluster layering], you create a `MachineOSConfig` object where you include the Containerfile and other parameters. The build is performed on your cluster and the resulting custom layered image is automatically pushed to your repository and applied to the machine config pool that you specified in the `MachineOSConfig` object. The entire process is performed completely within your cluster.
-+
---
-:FeatureName: On-cluster image layering
-include::snippets/technology-preview.adoc[]
---
 
 Out-of-cluster layering:: With xref:../machine_configuration/mco-coreos-layering.adoc#coreos-layering-configuring_mco-coreos-layering[out-of-cluster layering], you create a Containerfile that references an {product-title} image and the RPM that you want to apply, build the layered image in your own environment, and push the image to your repository. Then, in your cluster, create a `MachineConfig` object for the targeted node pool that points to the new image. The Machine Config Operator overrides the base {op-system} image, as specified by the `osImageURL` value in the associated machine config, and boots the new image.