Skip to content

Commit df81b73

Browse files
lahinsonlahinson
committed
[OSDOCS-15018]: Updating HCP support matrix for 4.19
1 parent 34f45db commit df81b73

File tree

1 file changed

+93
-31
lines changed

1 file changed

+93
-31
lines changed

‎modules/hcp-support-matrix.adoc

Lines changed: 93 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,9 @@ The following table maps {mce-short} versions to the management cluster versions
4040

4141
|4.16 - 4.18
4242
|2.8
43+
44+
|4.17 - 4.19
45+
|2.9
4346
|===
4447

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

5053
[NOTE]
5154
====
52-
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.
55+
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.
5356
====
5457

55-
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}:
58+
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}:
5659

5760
[NOTE]
5861
====
59-
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].
62+
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].
6063
====
6164

62-
.Hosted cluster versions that can be created by {mce-short} versions
63-
[cols="6",options="header"]
65+
.Hosted cluster version mapped to HyperShift Operator associated with {mce-short} version
66+
[cols="7",options="header"]
6467
|===
65-
|Hosted cluster version |{mce-short} 2.4 |{mce-short} 2.5 |{mce-short} 2.6 |{mce-short} 2.7|{mce-short} 2.8
68+
|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
6669

6770
|4.14
6871
|Yes
6972
|Yes
7073
|Yes
7174
|Yes
7275
|Yes
76+
|Yes
7377

7478
|4.15
7579
|No
7680
|Yes
7781
|Yes
7882
|Yes
7983
|Yes
84+
|Yes
8085

8186
|4.16
8287
|No
8388
|No
8489
|Yes
8590
|Yes
8691
|Yes
92+
|Yes
8793

8894
|4.17
8995
|No
9096
|No
9197
|No
9298
|Yes
9399
|Yes
100+
|Yes
94101

95102
|4.18
96103
|No
97104
|No
98105
|No
99106
|No
100107
|Yes
108+
|Yes
109+
110+
|4.19
111+
|No
112+
|No
113+
|No
114+
|No
115+
|No
116+
|Yes
101117
|===
102118

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

122138
|{aws-full}
123-
|4.16 - 4.18
124-
|4.16 - 4.18
139+
|4.16 - 4.19
140+
|4.16 - 4.19
125141

126142
|{ibm-power-title}
127-
|4.17 - 4.18
128-
|4.17 - 4.18
143+
|4.17 - 4.19
144+
|4.17 - 4.19
129145

130146
|{ibm-z-title}
131-
|4.17 - 4.18
132-
|4.17 - 4.18
147+
|4.17 - 4.19
148+
|4.17 - 4.19
133149

134150
|{VirtProductName}
135-
|4.14 - 4.18
136-
|4.14 - 4.18
151+
|4.14 - 4.19
152+
|4.14 - 4.19
137153

138154
|Bare metal
139-
|4.14 - 4.18
140-
|4.14 - 4.18
155+
|4.14 - 4.19
156+
|4.14 - 4.19
141157

142158
|Non-bare-metal agent machines (Technology Preview)
143-
|4.16 - 4.18
144-
|4.16 - 4.18
159+
|4.16 - 4.19
160+
|4.16 - 4.19
145161

146162
|{rh-openstack-first} (Technology Preview)
147163
|4.19
@@ -156,7 +172,11 @@ The following tables indicate the support status for {hcp} on multiple architect
156172
.Multi-architecture support for {hcp} on {aws-short}
157173
[cols="3",options="header"]
158174
|===
159-
|{product-title} version |ARM64 control planes |ARM64 worker nodes
175+
|{product-title} version |ARM64 control planes |ARM64 compute nodes
176+
177+
|4.19
178+
|General Availability
179+
|General Availability
160180

161181
|4.18
162182
|General Availability
@@ -182,7 +202,11 @@ The following tables indicate the support status for {hcp} on multiple architect
182202
.Multi-architecture support for {hcp} on bare metal
183203
[cols="3",options="header"]
184204
|===
185-
|{product-title} version |ARM64 control planes |ARM64 worker nodes
205+
|{product-title} version |ARM64 control planes |ARM64 compute nodes
206+
207+
|4.19
208+
|Not available
209+
|Technology Preview
186210

187211
|4.18
188212
|Not available
@@ -208,7 +232,11 @@ The following tables indicate the support status for {hcp} on multiple architect
208232
.Multi-architecture support for {hcp} on non-bare-metal agent machines
209233
[cols="3",options="header"]
210234
|===
211-
|{product-title} version |ARM64 control planes |ARM64 worker nodes
235+
|{product-title} version |ARM64 control planes |ARM64 compute nodes
236+
237+
|4.19
238+
|Not available
239+
|Not available
212240

213241
|4.18
214242
|Not available
@@ -222,21 +250,47 @@ The following tables indicate the support status for {hcp} on multiple architect
222250
.Multi-architecture support for {hcp} on {ibm-power-title}
223251
[cols="3",options="header"]
224252
|===
225-
|{product-title} version |ARM64 control planes |ARM64 worker nodes
253+
|{product-title} version |Control planes |Compute nodes
254+
255+
|4.19
256+
a|* 64-bit x86: General Availability
257+
* ARM64: Not available
258+
* s390x: Not available
259+
* ppc64le: Not available
260+
a|* 64-bit x86: General Availability
261+
* ARM64: Not available
262+
* s390x: Not available
263+
* ppc64le: General Availability
226264

227265
|4.18
228-
|Not available
229-
|Not available
266+
a|* 64-bit x86: General Availability
267+
* ARM64: Not available
268+
* s390x: Not available
269+
* ppc64le: Not available
270+
a|* 64-bit x86: Not available
271+
* ARM64: Not available
272+
* s390x: Not available
273+
* ppc64le: General Availability
230274

231275
|4.17
232-
|Not available
233-
|Not available
276+
a|* 64-bit x86: General Availability
277+
* ARM64: Not available
278+
* s390x: Not available
279+
* ppc64le: Not available
280+
a|* 64-bit x86: Not available
281+
* ARM64: Not available
282+
* s390x: Not available
283+
* ppc64le: General Availability
234284
|===
235285

236286
.Multi-architecture support for {hcp} on {ibm-z-title}
237287
[cols="3",options="header"]
238288
|===
239-
|{product-title} version |ARM64 control planes |ARM64 worker nodes
289+
|{product-title} version |ARM64 control planes |ARM64 compute nodes
290+
291+
|4.19
292+
|Not available
293+
|Not available
240294

241295
|4.18
242296
|Not available
@@ -250,7 +304,11 @@ The following tables indicate the support status for {hcp} on multiple architect
250304
.Multi-architecture support for {hcp} on {VirtProductName}
251305
[cols="3",options="header"]
252306
|===
253-
|{product-title} version |ARM64 control planes |ARM64 worker nodes
307+
|{product-title} version |ARM64 control planes |ARM64 compute nodes
308+
309+
|4.19
310+
|Not available
311+
|Not available
254312

255313
|4.18
256314
|Not available
@@ -281,7 +339,7 @@ When you update to another version of the {mce-short}, your hosted cluster can c
281339

282340
[NOTE]
283341
====
284-
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].
342+
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].
285343
====
286344

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

301359
|Updated from 2.7 to 2.8
302360
|{product-title} 4.14 - 4.17
361+
362+
|Updated from 2.8 to 2.9
363+
|{product-title} 4.14 - 4.18
303364
|===
304365

305366
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.
306367

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

310-
The following list indicates Technology Preview features for this release:
371+
The following list indicates features in this release that have a Technology Preview status:
311372

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

0 commit comments

Comments
 (0)