Merge pull request #92844 from mburke5678/mco-ocl-sno

OSDOCS:14528 Docs for On Cluster Layering and a seamless SNO experience/Disconnected Support

Author: mburke5678

modules/coreos-layering-configuring-on.adoc

@@ -40,6 +40,11 @@ You should not need to interact with these new objects or the `machine-os-builde
 
 You need a separate `MachineOSConfig` CR for each machine config pool where you want to use a custom layered image.
 
+[NOTE]
+====
+For {sno} clusters, you can apply a custom layered image to the control plane node only.
+====
+
 :FeatureName: On-cluster image layering
 include::snippets/technology-preview.adoc[]
 include::snippets//coreos-layering-configuring-on-pause.adoc[]
@@ -63,7 +68,7 @@ layered-c8765e26ebc87e1e17a7d6e0a78e8bae   False      False      False        Fa
 Note the following limitations when working with the on-cluster layering feature:
 
 * On-cluster layering is supported only for {product-title} clusters on the AMD64 architecture.
-* On-cluster layering is not supported on multi-architecture compute machines, {sno}, or disconnected clusters.
+* On-cluster layering is not supported on multi-architecture compute machines.
 * If you scale up a machine set that uses a custom layered image, the nodes reboot two times. The first, when the node is initially created with the base image and a second time when the custom layered image is applied.
 * Node disruption policies are not supported on nodes with a custom layered image. As a result the following configuration changes cause a node reboot:
 ** Modifying the configuration files in the `/var` or `/etc` directory
@@ -83,6 +88,11 @@ Note the following limitations when working with the on-cluster layering feature
 // If you are using the global pull secret, the MCO automatically creates a copy when you first create a `MachineOSconfig` object.
 
 * You have the push secret of the registry that the MCO needs to push the new custom layered image to.
++
+[NOTE]
+====
+In a disconnected environment, ensure that the disconnected cluster can access the registry where you want to push the image. Image mirroring applies only to pulling images.
+====
 
 * You have a pull secret that your nodes need to pull the new custom layered image from your registry. This should be a different secret than the one used to push the image to the repository.