[OSDOCS-13527]: Updating HCP support matrix for 4.18

Author: lahinson

modules/hcp-support-matrix.adoc

@@ -37,6 +37,9 @@ The following table maps {mce-short} versions to the management cluster versions
 
 |4.15 - 4.17
 |2.7
+
+|4.16 - 4.18
+|2.8
 |===
 
 [id="hcp-matrix-hc_{context}"]
@@ -51,82 +54,105 @@ Ensure a maximum latency of 200 ms between the management cluster and hosted clu
 
 The following table maps {mce-short} versions to the hosted cluster versions that you can create by using the HyperShift Operator that is associated with that version of {mce-short}:
 
+[NOTE]
+====
+Although the HyperShift Operator supports the hosted cluster versions in the following table, {mce-short} supports only as far back as 2 versions earlier than the current version. For example, if the current hosted cluster version is 4.18, {mce-short} supports as far back as version 4.16. If you want to use a hosted cluster version that is earlier than one of the versions that {mce-short} supports, you can detach your hosted clusters from {mce-short} to be unmanaged, or you can use an earlier version of {mce-short}. For more information, see link:https://access.redhat.com/articles/7099674[The multicluster engine for Kubernetes operator 2.8 Support Matrix].
+====
+
 .Hosted cluster versions that can be created by {mce-short} versions
-[cols="5",options="header"]
+[cols="6",options="header"]
 |===
-|Hosted cluster version  |{mce-short} 2.4 |{mce-short} 2.5 |{mce-short} 2.6 |{mce-short} 2.7
+|Hosted cluster version |{mce-short} 2.4 |{mce-short} 2.5 |{mce-short} 2.6 |{mce-short} 2.7|{mce-short} 2.8
 
 |4.14
 |Yes
 |Yes
 |Yes
 |Yes
+|Yes
 
 |4.15
 |No
 |Yes
 |Yes
 |Yes
+|Yes
 
 |4.16
 |No
 |No
 |Yes
 |Yes
+|Yes
 
 |4.17
 |No
 |No
 |No
 |Yes
+|Yes
+
+|4.18
+|No
+|No
+|No
+|No
+|Yes
 |===
 
 [id="hcp-matrix-platform_{context}"]
 == Hosted cluster platform support
 
+A hosted cluster supports only one infrastructure platform. For example, you cannot create multiple node pools on different infrastructure platforms.
+
 The following table indicates which {product-title} versions are supported for each platform of {hcp}.
 
 [IMPORTANT]
 ====
 For {ibm-power-title} and {ibm-z-title}, you must run the control plane on machine types based on 64-bit x86 architecture, and node pools on {ibm-power-title} or {ibm-z-title}.
 ====
 
-In the following table, Management cluster version refers to the {product-title} version where the {mce-short} is enabled:
+In the following table, the management cluster version is the {product-title} version where the {mce-short} is enabled:
 
 .Required {product-title} versions for platforms
 [cols="3",options="header"]
 |===
 |Hosted cluster platform |Management cluster version |Hosted cluster version
 
 |{aws-full}
-|4.16 - 4.17
-|4.16 - 4.17
+|4.16 - 4.18
+|4.16 - 4.18
 
 |{ibm-power-title}
-|4.17
-|4.17
+|4.17 - 4.18
+|4.17 - 4.18
 
 |{ibm-z-title}
-|4.17
-|4.17
+|4.17 - 4.18
+|4.17 - 4.18
 
 |{VirtProductName}
-|4.14 - 4.17
-|4.14 - 4.17
+|4.14 - 4.18
+|4.14 - 4.18
 
 |Bare metal
-|4.14 - 4.17
-|4.14 - 4.17
+|4.14 - 4.18
+|4.14 - 4.18
 
 |Non-bare-metal agent machines (Technology Preview)
-|4.16 - 4.17
-|4.16 - 4.17
+|4.16 - 4.18
+|4.16 - 4.18
 |===
 
 [id="hcp-matrix-updates_{context}"]
 == Updates of {mce-short}
 
-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:
+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.
+
+[NOTE]
+====
+Although the HyperShift Operator supports the hosted cluster versions in the following table, {mce-short} supports only as far back as 2 versions earlier than the current version. For example, if the current hosted cluster version is 4.18, {mce-short} supports as far back as version 4.16. If you want to use a hosted cluster version that is earlier than one of the versions that {mce-short} supports, you can detach your hosted clusters from {mce-short} to be unmanaged, or you can use an earlier version of {mce-short}. For more information, see link:https://access.redhat.com/articles/7099674[The multicluster engine for Kubernetes operator 2.8 Support Matrix].
+====
 
 .Updated {mce-short} version support for hosted clusters
 [cols="2",options="header"]
@@ -141,6 +167,9 @@ When you update to another version of the {mce-short}, your hosted cluster can c
 
 |Updated from 2.6 to 2.7
 |{product-title} 4.14 - 4.16
+
+|Updated from 2.7 to 2.8
+|{product-title} 4.14 - 4.17
 |===
 
 For example, if you have an {product-title} 4.14 hosted cluster on the management cluster and you update from {mce-short} 2.4 to 2.5, the hosted cluster can continue to run.
@@ -152,4 +181,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}