SNO is not supported for a mgmt cluster in HCP

Author: xenolinux

hosted_control_planes/hcp-prepare/hcp-requirements.adoc

@@ -15,4 +15,5 @@ include::modules/hcp-support-matrix.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 * link:https://access.redhat.com/articles/7086906[The {mce} 2.7 support matrix]
-* link:https://access.redhat.com/labs/ocpouic/?operator=multicluster-engine&&upgrade_path=4.14%20to%204.16[Red{nbsp}Hat {product-title} Operator Update Information Checker]
+* link:https://access.redhat.com/labs/ocpouic/?operator=multicluster-engine&&upgrade_path=4.14%20to%204.16[Red{nbsp}Hat {product-title} Operator Update Information Checker]
+* xref:../../hosted_control_planes/hcp-prepare/hcp-sizing-guidance.adoc#hcp-shared-infra_hcp-sizing-guidance[Shared infrastructure between hosted and standalone control planes]

modules/hcp-support-matrix.adoc

@@ -12,7 +12,14 @@ Because {mce} includes the HyperShift Operator, releases of {hcp} align with rel
 [id="hcp-matrix-mgmt_{context}"]
 == Management cluster support
 
-Any supported standalone {product-title} cluster can be a management cluster. The following table maps {mce-short} versions to the management cluster versions that support them:
+Any supported standalone {product-title} cluster can be a management cluster.
+
+[NOTE]
+====
+A single-node {product-title} cluster is not supported as a management cluster. If you have resource constraints, you can share infrastructure between a standalone {product-title} control plane and {hcp}. For more information, see "Shared infrastructure between hosted and standalone control planes".
+====
+
+The following table maps {mce-short} versions to the management cluster versions that support them:
 
 .Supported {mce-short} versions for {product-title} management clusters
 [cols="2",options="header"]
@@ -35,7 +42,7 @@ Any supported standalone {product-title} cluster can be a management cluster. Th
 [id="hcp-matrix-hc_{context}"]
 == Hosted cluster support
 
-For hosted clusters, no direct relationship exists between the management cluster version and the hosted cluster version. The hosted cluster version depends on the HyperShift Operator that is included with your {mce-short} version. 
+For hosted clusters, no direct relationship exists between the management cluster version and the hosted cluster version. The hosted cluster version depends on the HyperShift Operator that is included with your {mce-short} version.
 
 [NOTE]
 ====
@@ -114,7 +121,7 @@ The following table indicates which {product-title} versions are supported for e
 
 When you update to another version of the {mce-short}, your hosted cluster can continue to run if the HyperShift Operator that is included in the version of {mce-short} supports the hosted cluster version. The following table shows which hosted cluster versions are supported on which updated {mce-short} versions:
 
-.Updated {mce-short} version support for hosted clusters 
+.Updated {mce-short} version support for hosted clusters
 [cols="2",options="header"]
 |===
 |Updated {mce-short} version |Supported hosted cluster version
@@ -138,4 +145,4 @@ The following list indicates Technology Preview features for this release:
 
 * {hcp-capital} on {ibm-z-title} in a disconnected environment
 * Custom taints and tolerations for {hcp} on {VirtProductName}
-* NVIDIA GPU devices on {hcp} for {VirtProductName}
+* NVIDIA GPU devices on {hcp} for {VirtProductName}