You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hosted_control_planes/hcp-prepare/hcp-requirements.adoc
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,10 @@ The following requirements apply to {hcp}:
22
22
23
23
* 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.
* 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]
33
35
* xref:../../hosted_control_planes/hcp-prepare/hcp-sizing-guidance.adoc#hcp-shared-infra_hcp-sizing-guidance[Shared infrastructure between hosted and standalone control planes]
Copy file name to clipboardExpand all lines: modules/hcp-support-matrix.adoc
+74-38Lines changed: 74 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,12 +26,6 @@ The following table maps {mce-short} versions to the management cluster versions
26
26
|===
27
27
|Management cluster version |Supported {mce-short} version
28
28
29
-
|4.14 - 4.15
30
-
|2.4
31
-
32
-
|4.14 - 4.16
33
-
|2.5
34
-
35
29
|4.14 - 4.17
36
30
|2.6
37
31
@@ -43,6 +37,9 @@ The following table maps {mce-short} versions to the management cluster versions
43
37
44
38
|4.17 - 4.19
45
39
|2.9
40
+
41
+
|4.18 - 4.20
42
+
|2.10
46
43
|===
47
44
48
45
[id="hcp-matrix-hc_{context}"]
@@ -59,58 +56,59 @@ The following table shows the hosted cluster versions that you can create by usi
59
56
60
57
[NOTE]
61
58
====
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] (Red{nbsp}Hat Knowledgebase).
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.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).
63
60
====
64
61
65
62
.Hosted cluster version mapped to HyperShift Operator associated with {mce-short} version
66
-
[cols="7",options="header"]
63
+
[cols="6",options="header"]
67
64
|===
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
65
+
|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
69
66
70
67
|4.14
71
68
|Yes
72
69
|Yes
73
70
|Yes
74
71
|Yes
75
72
|Yes
76
-
|Yes
77
73
78
74
|4.15
79
-
|No
80
75
|Yes
81
76
|Yes
82
77
|Yes
83
78
|Yes
84
79
|Yes
85
80
86
81
|4.16
87
-
|No
88
-
|No
82
+
|Yes
89
83
|Yes
90
84
|Yes
91
85
|Yes
92
86
|Yes
93
87
94
88
|4.17
95
89
|No
96
-
|No
97
-
|No
90
+
|Yes
98
91
|Yes
99
92
|Yes
100
93
|Yes
101
94
102
95
|4.18
103
96
|No
104
97
|No
105
-
|No
106
-
|No
98
+
|Yes
107
99
|Yes
108
100
|Yes
109
101
110
102
|4.19
111
103
|No
112
104
|No
113
105
|No
106
+
|Yes
107
+
|Yes
108
+
109
+
|4.20
110
+
|No
111
+
|No
114
112
|No
115
113
|No
116
114
|Yes
@@ -125,7 +123,10 @@ The following table indicates which {product-title} versions are supported for e
125
123
126
124
[IMPORTANT]
127
125
====
128
-
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}.
126
+
For {ibm-power-title} and {ibm-z-title}:
127
+
128
+
* You must run the control plane on machine types that are based on 64-bit x86 architecture or s390x architecture
129
+
* You must run node pools on {ibm-power-title} or {ibm-z-title}
129
130
====
130
131
131
132
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
136
137
|Hosted cluster platform |Management cluster version |Hosted cluster version
@@ -174,6 +175,10 @@ The following tables indicate the support status for {hcp} on multiple architect
174
175
|===
175
176
|{product-title} version |ARM64 control planes |ARM64 compute nodes
176
177
178
+
|4.20
179
+
|General Availability
180
+
|General Availability
181
+
177
182
|4.19
178
183
|General Availability
179
184
|General Availability
@@ -204,6 +209,10 @@ The following tables indicate the support status for {hcp} on multiple architect
204
209
|===
205
210
|{product-title} version |ARM64 control planes |ARM64 compute nodes
206
211
212
+
|4.20
213
+
|Not available
214
+
|Technology Preview
215
+
207
216
|4.19
208
217
|Not available
209
218
|Technology Preview
@@ -234,6 +243,10 @@ The following tables indicate the support status for {hcp} on multiple architect
234
243
|===
235
244
|{product-title} version |ARM64 control planes |ARM64 compute nodes
236
245
246
+
|4.20
247
+
|Not available
248
+
|Not available
249
+
237
250
|4.19
238
251
|Not available
239
252
|Not available
@@ -252,6 +265,16 @@ The following tables indicate the support status for {hcp} on multiple architect
252
265
|===
253
266
|{product-title} version |Control planes |Compute nodes
254
267
268
+
|4.20
269
+
a|* 64-bit x86: General Availability
270
+
* ARM64: Not available
271
+
* s390x: Not available
272
+
* ppc64le: Not available
273
+
a|* 64-bit x86: General Availability
274
+
* ARM64: Not available
275
+
* s390x: Not available
276
+
* ppc64le: General Availability
277
+
255
278
|4.19
256
279
a|* 64-bit x86: General Availability
257
280
* ARM64: Not available
@@ -288,6 +311,15 @@ a|* 64-bit x86: Not available
288
311
|===
289
312
|{product-title} version |Control planes |Compute nodes
290
313
314
+
|4.20
315
+
a|* 64-bit x86: General Availability
316
+
* ARM64: Not available
317
+
* s390x: General Availability
318
+
* ppc64le: Not available
319
+
a|* 64-bit x86: Not available
320
+
* ARM64: Not available
321
+
* s390x: General Availability
322
+
291
323
|4.19
292
324
a|* 64-bit x86: General Availability
293
325
* ARM64: Not available
@@ -323,6 +355,10 @@ a|* 64-bit x86: Not available
323
355
|===
324
356
|{product-title} version |ARM64 control planes |ARM64 compute nodes
325
357
358
+
|4.20
359
+
|Not available
360
+
|Not available
361
+
326
362
|4.19
327
363
|Not available
328
364
|Not available
@@ -356,17 +392,14 @@ When you update to another version of the {mce-short}, your hosted cluster can c
356
392
357
393
[NOTE]
358
394
====
359
-
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).
395
+
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).
360
396
====
361
397
362
398
.Updated {mce-short} version support for hosted clusters
363
399
[cols="2",options="header"]
364
400
|===
365
401
|Updated {mce-short} version |Supported hosted cluster version
366
402
367
-
|Updated from 2.4 to 2.5
368
-
|{product-title} 4.14
369
-
370
403
|Updated from 2.5 to 2.6
371
404
|{product-title} 4.14 - 4.15
372
405
@@ -378,16 +411,19 @@ Although the HyperShift Operator supports the hosted cluster versions in the fol
378
411
379
412
|Updated from 2.8 to 2.9
380
413
|{product-title} 4.14 - 4.18
414
+
415
+
|Updated from 2.9 to 2.10
416
+
|{product-title} 4.14 - 4.19
381
417
|===
382
418
383
-
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.
419
+
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.
384
420
385
421
[id="hcp-matrix-tp_{context}"]
386
422
== Technology Preview features
387
423
388
424
The following list indicates features in this release that have a Technology Preview status:
389
425
390
-
* {hcp-capital} on {ibm-z-title} in a disconnected environment
426
+
* {hcp-capital} using non-bare-metal agent machines
391
427
* Custom taints and tolerations for {hcp}
392
428
* NVIDIA GPU devices on {hcp} for {VirtProductName}
0 commit comments