Skip to content

[OSDOCS-15018]: Updating HCP support matrix for 4.19 #95127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+114 −35
Open

[OSDOCS-15018]: Updating HCP support matrix for 4.19 #95127

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
149 changes: 114 additions & 35 deletions modules/hcp-support-matrix.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,9 @@ The following table maps {mce-short} versions to the management cluster versions

|4.16 - 4.18
|2.8

|4.17 - 4.19
|2.9
|===

[id="hcp-matrix-hc_{context}"]
Expand All @@ -49,55 +52,68 @@ For hosted clusters, no direct relationship exists between the management cluste

[NOTE]
====
Ensure a maximum latency of 200 ms between the management cluster and hosted clusters. This requirement is especially important for mixed infrastructure deployments, such as when your management cluster is on {aws-short} and your worker nodes are on-premise.
Ensure a maximum latency of 200 ms between the management cluster and hosted clusters. This requirement is especially important for mixed infrastructure deployments, such as when your management cluster is on {aws-short} and your compute nodes are on-premise.
====

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}:
The following table shows the hosted cluster versions that you can create by using the HyperShift Operator that is associated with a 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.19, {mce-short} supports as far back as version 4.17. 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].
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.19, {mce-short} supports as far back as version 4.17. 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 instructions to detach your hosted clusters from {mce-short}, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#remove-managed-cluster[Removing a cluster from management] ({rh-rhacm} documentation). For more information about {mce-short} support, see link:https://access.redhat.com/articles/7120837[The multicluster engine for Kubernetes operator 2.9 Support Matrix] (Red{nbsp}Hat Knowledgebase).
====

.Hosted cluster versions that can be created by {mce-short} versions
[cols="6",options="header"]
.Hosted cluster version mapped to HyperShift Operator associated with {mce-short} version
[cols="7",options="header"]
|===
|Hosted cluster version |{mce-short} 2.4 |{mce-short} 2.5 |{mce-short} 2.6 |{mce-short} 2.7|{mce-short} 2.8
|Hosted cluster version |HyperShift Operator in {mce-short} 2.4 |HyperShift Operator in {mce-short} 2.5 |HyperShift Operator in {mce-short} 2.6 |HyperShift Operator in {mce-short} 2.7|HyperShift Operator in {mce-short} 2.8|HyperShift Operator in {mce-short} 2.9

|4.14
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes

|4.15
|No
|Yes
|Yes
|Yes
|Yes
|Yes

|4.16
|No
|No
|Yes
|Yes
|Yes
|Yes

|4.17
|No
|No
|No
|Yes
|Yes
|Yes

|4.18
|No
|No
|No
|No
|Yes
|Yes

|4.19
|No
|No
|No
|No
|No
|Yes
|===

[id="hcp-matrix-platform_{context}"]
Expand All @@ -120,28 +136,28 @@ In the following table, the management cluster version is the {product-title} ve
|Hosted cluster platform |Management cluster version |Hosted cluster version

|{aws-full}
|4.16 - 4.18
|4.16 - 4.18
|4.16 - 4.19
|4.16 - 4.19

|{ibm-power-title}
|4.17 - 4.18
|4.17 - 4.18
|4.17 - 4.19
|4.17 - 4.19

|{ibm-z-title}
|4.17 - 4.18
|4.17 - 4.18
|4.17 - 4.19
|4.17 - 4.19

|{VirtProductName}
|4.14 - 4.18
|4.14 - 4.18
|4.14 - 4.19
|4.14 - 4.19

|Bare metal
|4.14 - 4.18
|4.14 - 4.18
|4.14 - 4.19
|4.14 - 4.19

|Non-bare-metal agent machines (Technology Preview)
|4.16 - 4.18
|4.16 - 4.18
|4.16 - 4.19
|4.16 - 4.19

|{rh-openstack-first} (Technology Preview)
|4.19
Expand All @@ -156,7 +172,11 @@ The following tables indicate the support status for {hcp} on multiple architect
.Multi-architecture support for {hcp} on {aws-short}
[cols="3",options="header"]
|===
|{product-title} version |ARM64 control planes |ARM64 worker nodes
|{product-title} version |ARM64 control planes |ARM64 compute nodes

|4.19
|General Availability
|General Availability

|4.18
|General Availability
Expand All @@ -182,7 +202,11 @@ The following tables indicate the support status for {hcp} on multiple architect
.Multi-architecture support for {hcp} on bare metal
[cols="3",options="header"]
|===
|{product-title} version |ARM64 control planes |ARM64 worker nodes
|{product-title} version |ARM64 control planes |ARM64 compute nodes

|4.19
|Not available
|Technology Preview

|4.18
|Not available
Expand All @@ -208,7 +232,11 @@ The following tables indicate the support status for {hcp} on multiple architect
.Multi-architecture support for {hcp} on non-bare-metal agent machines
[cols="3",options="header"]
|===
|{product-title} version |ARM64 control planes |ARM64 worker nodes
|{product-title} version |ARM64 control planes |ARM64 compute nodes

|4.19
|Not available
|Not available

|4.18
|Not available
Expand All @@ -222,35 +250,82 @@ The following tables indicate the support status for {hcp} on multiple architect
.Multi-architecture support for {hcp} on {ibm-power-title}
[cols="3",options="header"]
|===
|{product-title} version |ARM64 control planes |ARM64 worker nodes
|{product-title} version |Control planes |Compute nodes

|4.19
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: Not available
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: General Availability

|4.18
|Not available
|Not available
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: Not available
a|* 64-bit x86: Not available
* ARM64: Not available
* s390x: Not available
* ppc64le: General Availability

|4.17
|Not available
|Not available
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: Not available
a|* 64-bit x86: Not available
* ARM64: Not available
* s390x: Not available
* ppc64le: General Availability
|===

.Multi-architecture support for {hcp} on {ibm-z-title}
[cols="3",options="header"]
|===
|{product-title} version |ARM64 control planes |ARM64 worker nodes
|{product-title} version |Control planes |Compute nodes

|4.19
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: Not available
a|* 64-bit x86: Not available
* ARM64: Not available
* s390x: General Availability

|4.18
|Not available
|Not available
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: Not available
a|* 64-bit x86: Not available
* ARM64: Not available
* s390x: General Availability
* ppc64le: Not available

|4.17
|Not available
|Not available
a|* 64-bit x86: General Availability
* ARM64: Not available
* s390x: Not available
* ppc64le: Not available
a|* 64-bit x86: Not available
* ARM64: Not available
* s390x: General Availability
* ppc64le: Not available
|===

.Multi-architecture support for {hcp} on {VirtProductName}
[cols="3",options="header"]
|===
|{product-title} version |ARM64 control planes |ARM64 worker nodes
|{product-title} version |ARM64 control planes |ARM64 compute nodes

|4.19
|Not available
|Not available

|4.18
|Not available
Expand Down Expand Up @@ -281,7 +356,7 @@ When you update to another version of the {mce-short}, your hosted cluster can c

[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.19, {mce-short} supports as far back as version 4.17. 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].
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.19, {mce-short} supports as far back as version 4.17. 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 instructions to detach your hosted clusters from {mce-short}, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#remove-managed-cluster[Removing a cluster from management] ({rh-rhacm} documentation). For more information about {mce-short} support, see link:https://access.redhat.com/articles/7120837[The multicluster engine for Kubernetes operator 2.9 Support Matrix] (Red{nbsp}Hat Knowledgebase).
====

.Updated {mce-short} version support for hosted clusters
Expand All @@ -300,15 +375,19 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol

|Updated from 2.7 to 2.8
|{product-title} 4.14 - 4.17

|Updated from 2.8 to 2.9
|{product-title} 4.14 - 4.18
|===

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.

[id="hcp-matrix-tp_{context}"]
== Technology Preview features

The following list indicates Technology Preview features for this release:
The following list indicates features in this release that have a Technology Preview status:

* {hcp-capital} on {ibm-z-title} in a disconnected environment
* Custom taints and tolerations for {hcp}
* NVIDIA GPU devices on {hcp} for {VirtProductName}
* NVIDIA GPU devices on {hcp} for {VirtProductName}
* {hcp-capital} on {rh-openstack-first}