mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Updating HCP support matrix for 4.20
This commit is contained in:
Laura Hinson
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
d523789bc7
commit
31181c4915
@@ -22,8 +22,10 @@ The following requirements apply to {hcp}:
|
||||
|
||||
* In Bare Metal Host (BMH) deployments, where the Bare Metal Operator starts machines, the hosted control plane must be able to reach baseboard management controllers (BMCs). If your security profile does not permit the Cluster Baremetal Operator to access the network where the BMHs have their BMCs in order to enable Redfish automation, you can use BYO ISO support. However, in BYO mode, {product-title} cannot automate the powering on of BMHs.
|
||||
|
||||
//Support matrix for HCP
|
||||
include::modules/hcp-support-matrix.adoc[leveloffset=+1]
|
||||
|
||||
//FIPS-enabled hosted clusters
|
||||
include::modules/hcp-fips.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
@@ -32,9 +34,9 @@ include::modules/hcp-fips.adoc[leveloffset=+1]
|
||||
* 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]
|
||||
|
||||
//CIDR ranges for hosted control planes
|
||||
include::modules/hcp-cidr-ranges.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../networking/networking_overview/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions]
|
||||
|
||||
@@ -26,12 +26,6 @@ The following table maps {mce-short} versions to the management cluster versions
|
||||
|===
|
||||
|Management cluster version |Supported {mce-short} version
|
||||
|
||||
|4.14 - 4.15
|
||||
|2.4
|
||||
|
||||
|4.14 - 4.16
|
||||
|2.5
|
||||
|
||||
|4.14 - 4.17
|
||||
|2.6
|
||||
|
||||
@@ -43,6 +37,9 @@ The following table maps {mce-short} versions to the management cluster versions
|
||||
|
||||
|4.17 - 4.19
|
||||
|2.9
|
||||
|
||||
|4.18 - 4.20
|
||||
|2.10
|
||||
|===
|
||||
|
||||
[id="hcp-matrix-hc_{context}"]
|
||||
@@ -59,13 +56,13 @@ The following table shows the hosted cluster versions that you can create by usi
|
||||
|
||||
[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 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).
|
||||
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.20, {mce-short} supports as far back as version 4.18. 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.10 Support Matrix] (Red{nbsp}Hat Knowledgebase).
|
||||
====
|
||||
|
||||
.Hosted cluster version mapped to HyperShift Operator associated with {mce-short} version
|
||||
[cols="7",options="header"]
|
||||
[cols="6",options="header"]
|
||||
|===
|
||||
|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
|
||||
|Hosted cluster version |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 |HyperShift Operator in {mce-short} 2.10
|
||||
|
||||
|4.14
|
||||
|Yes
|
||||
@@ -73,10 +70,8 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
|
||||
|4.15
|
||||
|No
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
@@ -84,8 +79,7 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|Yes
|
||||
|
||||
|4.16
|
||||
|No
|
||||
|No
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
@@ -93,8 +87,7 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|
||||
|4.17
|
||||
|No
|
||||
|No
|
||||
|No
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
@@ -102,8 +95,7 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|4.18
|
||||
|No
|
||||
|No
|
||||
|No
|
||||
|No
|
||||
|Yes
|
||||
|Yes
|
||||
|Yes
|
||||
|
||||
@@ -111,6 +103,12 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|No
|
||||
|No
|
||||
|No
|
||||
|Yes
|
||||
|Yes
|
||||
|
||||
|4.20
|
||||
|No
|
||||
|No
|
||||
|No
|
||||
|No
|
||||
|Yes
|
||||
@@ -125,7 +123,10 @@ The following table indicates which {product-title} versions are supported for e
|
||||
|
||||
[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}.
|
||||
For {ibm-power-title} and {ibm-z-title}:
|
||||
|
||||
* You must run the control plane on machine types that are based on 64-bit x86 architecture or s390x architecture
|
||||
* You must run node pools on {ibm-power-title} or {ibm-z-title}
|
||||
====
|
||||
|
||||
In the following table, the management cluster version is the {product-title} version where the {mce-short} is enabled:
|
||||
@@ -136,32 +137,32 @@ 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.19
|
||||
|4.16 - 4.19
|
||||
|4.16 - 4.20
|
||||
|4.16 - 4.20
|
||||
|
||||
|{ibm-power-title}
|
||||
|4.17 - 4.19
|
||||
|4.17 - 4.19
|
||||
|4.17 - 4.20
|
||||
|4.17 - 4.20
|
||||
|
||||
|{ibm-z-title}
|
||||
|4.17 - 4.19
|
||||
|4.17 - 4.19
|
||||
|4.17 - 4.20
|
||||
|4.17 - 4.20
|
||||
|
||||
|{VirtProductName}
|
||||
|4.14 - 4.19
|
||||
|4.14 - 4.19
|
||||
|4.14 - 4.20
|
||||
|4.14 - 4.20
|
||||
|
||||
|Bare metal
|
||||
|4.14 - 4.19
|
||||
|4.14 - 4.19
|
||||
|4.14 - 4.20
|
||||
|4.14 - 4.20
|
||||
|
||||
|Non-bare-metal agent machines (Technology Preview)
|
||||
|4.16 - 4.19
|
||||
|4.16 - 4.19
|
||||
|4.16 - 4.20
|
||||
|4.16 - 4.20
|
||||
|
||||
|{rh-openstack-first} (Technology Preview)
|
||||
|4.19
|
||||
|4.19
|
||||
|4.19 - 4.20
|
||||
|4.19 - 4.20
|
||||
|===
|
||||
|
||||
[id="hcp-matrix-multiarch_{context}"]
|
||||
@@ -174,6 +175,10 @@ The following tables indicate the support status for {hcp} on multiple architect
|
||||
|===
|
||||
|{product-title} version |ARM64 control planes |ARM64 compute nodes
|
||||
|
||||
|4.20
|
||||
|General Availability
|
||||
|General Availability
|
||||
|
||||
|4.19
|
||||
|General Availability
|
||||
|General Availability
|
||||
@@ -204,6 +209,10 @@ The following tables indicate the support status for {hcp} on multiple architect
|
||||
|===
|
||||
|{product-title} version |ARM64 control planes |ARM64 compute nodes
|
||||
|
||||
|4.20
|
||||
|Not available
|
||||
|Technology Preview
|
||||
|
||||
|4.19
|
||||
|Not available
|
||||
|Technology Preview
|
||||
@@ -234,6 +243,10 @@ The following tables indicate the support status for {hcp} on multiple architect
|
||||
|===
|
||||
|{product-title} version |ARM64 control planes |ARM64 compute nodes
|
||||
|
||||
|4.20
|
||||
|Not available
|
||||
|Not available
|
||||
|
||||
|4.19
|
||||
|Not available
|
||||
|Not available
|
||||
@@ -252,6 +265,16 @@ The following tables indicate the support status for {hcp} on multiple architect
|
||||
|===
|
||||
|{product-title} version |Control planes |Compute nodes
|
||||
|
||||
|4.20
|
||||
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.19
|
||||
a|* 64-bit x86: General Availability
|
||||
* ARM64: Not available
|
||||
@@ -288,6 +311,15 @@ a|* 64-bit x86: Not available
|
||||
|===
|
||||
|{product-title} version |Control planes |Compute nodes
|
||||
|
||||
|4.20
|
||||
a|* 64-bit x86: General Availability
|
||||
* ARM64: Not available
|
||||
* s390x: General Availability
|
||||
* ppc64le: Not available
|
||||
a|* 64-bit x86: Not available
|
||||
* ARM64: Not available
|
||||
* s390x: General Availability
|
||||
|
||||
|4.19
|
||||
a|* 64-bit x86: General Availability
|
||||
* ARM64: Not available
|
||||
@@ -323,6 +355,10 @@ a|* 64-bit x86: Not available
|
||||
|===
|
||||
|{product-title} version |ARM64 control planes |ARM64 compute nodes
|
||||
|
||||
|4.20
|
||||
|Not available
|
||||
|Not available
|
||||
|
||||
|4.19
|
||||
|Not available
|
||||
|Not available
|
||||
@@ -356,7 +392,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 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).
|
||||
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.20, {mce-short} supports as far back as version 4.18. 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.10 Support Matrix] (Red{nbsp}Hat Knowledgebase).
|
||||
====
|
||||
|
||||
.Updated {mce-short} version support for hosted clusters
|
||||
@@ -364,9 +400,6 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|===
|
||||
|Updated {mce-short} version |Supported hosted cluster version
|
||||
|
||||
|Updated from 2.4 to 2.5
|
||||
|{product-title} 4.14
|
||||
|
||||
|Updated from 2.5 to 2.6
|
||||
|{product-title} 4.14 - 4.15
|
||||
|
||||
@@ -378,16 +411,19 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
|
||||
|
||||
|Updated from 2.8 to 2.9
|
||||
|{product-title} 4.14 - 4.18
|
||||
|
||||
|Updated from 2.9 to 2.10
|
||||
|{product-title} 4.14 - 4.19
|
||||
|===
|
||||
|
||||
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.
|
||||
For example, if you have an {product-title} 4.18 hosted cluster on the management cluster and you update from {mce-short} 2.8 to 2.9, the hosted cluster can continue to run.
|
||||
|
||||
[id="hcp-matrix-tp_{context}"]
|
||||
== Technology Preview features
|
||||
|
||||
The following list indicates features in this release that have a Technology Preview status:
|
||||
|
||||
* {hcp-capital} on {ibm-z-title} in a disconnected environment
|
||||
* {hcp-capital} using non-bare-metal agent machines
|
||||
* Custom taints and tolerations for {hcp}
|
||||
* NVIDIA GPU devices on {hcp} for {VirtProductName}
|
||||
* {hcp-capital} on {rh-openstack-first}
|
||||
Reference in New Issue
Block a user