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
* xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-hcp-service-definition[Regions and availability zones]
20
21
22
+
endif::openshift-rosa-hcp[]
23
+
21
24
* xref:../rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-security-regulation-compliance_rosa-policy-process-security[Security and regulation compliance]
xref:../../rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding process and security]
93
93
endif::openshift-rosa-hcp[]
94
-
|
94
+
95
+
ifdef::openshift-rosa-hcp[]
95
96
xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-hcp-service-definition[{hcp-title} service definition]
//Adding conditions around these in case the Additional resources don't get ported to HCP or have different file names / locations; keeping all included for now
26
+
//Adding conditions around these in case the Additional resources don't get ported to HCP or have different file names / locations; keeping all included for now
Copy file name to clipboardExpand all lines: rosa_release_notes/rosa-release-notes.adoc
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,7 +115,7 @@ endif::openshift-rosa[]
115
115
//* **Egress zero is now generally available on {product-title} clusters.** You can create a fully operational cluster that does not require a public egress by configuring a virtual private cloud (VPC) and using the `--properties zero_egress:true` flag when creating your cluster. For more information, see xref:../rosa_hcp/rosa-hcp-egress-zero-install.adoc#rosa-hcp-egress-zero-install[Creating a {egress-zero-title}].
116
116
//endif::openshift-rosa-hcp[]
117
117
118
-
//Commenting this out as is repeated above, although version type is slightly different.Out of scope for Whats new pruning task. Will investigate separately.
118
+
//Commenting this out as is repeated above, although version type is slightly different.Out of scope for Whats new pruning task. Will investigate separately.
119
119
//* **{product-title} SDN network plugin blocks future major upgrades**
120
120
//* **Initiate live migration from OpenShift SDN to OVN-Kubernetes.**
121
121
//As part of the {product-title} move to OVN-Kubernetes as the only supported network plugin starting with {product-title} version 4.17, users can now initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
@@ -174,7 +174,12 @@ ifdef::openshift-rosa-hcp[]
174
174
175
175
* **{product-title} Graviton Arm-based instance types.** You can now use {AWS} Arm-based Graviton instance types for your workloads in {product-title} clusters created after 24 July, 2024. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-sdpolicy-aws-instance-types-graviton_rosa-hcp-instance-types[AWS Graviton Arm-based instance types].
176
176
endif::openshift-rosa-hcp[]
177
-
177
+
// ifdef::openshift-rosa-hcp[]
178
+
// * **Upgrade multiple nodes simultaneously.** You can now configure a machine pool to upgrade multiple nodes simultaneously. Two new machine pool parameters, `max-surge` and `max-unavailable`, give you greater control over how machine pool upgrades occur. For more information, see xref:../upgrading/rosa-hcp-upgrading.adoc#rosa-hcp-upgrading[Upgrading {hcp-title} clusters].
179
+
// endif::openshift-rosa-hcp[]
180
+
ifdef::openshift-rosa-hcp[]
181
+
* **{hcp-title} Graviton Arm-based instance types.** You can now use {AWS} Arm-based Graviton instance types for your workloads in {hcp-title-first} clusters created after 24 July, 2024. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-sdpolicy-aws-instance-types-graviton_rosa-hcp-instance-types[AWS Graviton Arm-based instance types].
182
+
endif::openshift-rosa-hcp[]
178
183
* **ROSA CLI update.** The ROSA CLI (`rosa`) was updated to a new version. For information about what has changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.42[ROSA CLI release notes]. For more information about the ROSA CLI (`rosa`), see xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-about_rosa-getting-started-cli[About the ROSA CLI].
179
184
180
185
[id="rosa-q2-2024_{context}"]
@@ -200,6 +205,8 @@ ifdef::openshift-rosa[]
200
205
endif::openshift-rosa[]
201
206
ifdef::openshift-rosa-hcp[]
202
207
* **{product-title} regions added.** {product-title} is now available in the following regions:
208
+
ifdef::openshift-rosa-hcp[]
209
+
* **{hcp-title} regions added.** {hcp-title-first} is now available in the following regions:
203
210
+
204
211
** Zurich (`eu-central-2`)
205
212
** Hong Kong (`ap-east-1`)
@@ -211,6 +218,8 @@ For more information on region availabilities, see xref:../rosa_architecture/ros
211
218
212
219
* **Added support for external authentication providers.** You can now create clusters configured with external authentication providers, such as Microsoft Entra ID and KeyCloak. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc#rosa-hcp-sts-creating-a-cluster-ext-auth[Creating {product-title} clusters with external authentication].
213
220
endif::openshift-rosa-hcp[]
221
+
endif::openshift-rosa-hcp[]
222
+
* **Added support for external authentication providers.** You can now create clusters configured with external authentication providers, such as Microsoft Entra ID and KeyCloak. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc#rosa-hcp-sts-creating-a-cluster-ext-auth[Creating ROSA with HCP clusters with external authentication].
214
223
215
224
* **Longer cluster names enhancement.** You can now specify a cluster name that is longer than 15 characters. For cluster names that are longer than 15 characters, you can customize the domain prefix for the cluster URL by using the `domain-prefix` flag in the ROSA CLI (`rosa`) or by selecting the **Create custom domain prefix** checkbox in the {hybrid-console}. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-create-cluster-command_rosa-managing-objects-cli[create cluster in Managing objects with the ROSA CLI].
216
225
@@ -297,13 +306,16 @@ ifdef::openshift-rosa[]
297
306
* **Machine pool update.** You can now add taints to the machine pool that is automatically generated during cluster creation. You can also delete this machine pool. This new feature provides more flexibility and cost-effectiveness for cluster administrators, specifically in regards to scaling infrastructure based on changing resource requirements. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_a_machine_pool_rosa-managing-worker-nodes[Creating a machine pool].
298
307
299
308
* **{product-title} regions added.** {product-title} is now available in the following regions:
309
+
ifdef::openshift-rosa-hcp[]
310
+
* **ROSA regions added.** {product-title} (ROSA) is now available in the following regions:
300
311
+
301
312
** Spain (`eu-south-2`)
302
313
** Hyderabad (`ap-south-2`)
303
314
** Melbourne (`ap-southeast-4`)
304
315
** Zurich (`eu-central-2`)
305
316
+
306
317
For more information on region availabilities, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
318
+
endif::openshift-rosa-hcp[]
307
319
308
320
* **Documentation update.** The CLI Tools section was added to the ROSA documentation and includes more detailed information to help you fully use all of the supported CLI tools. The ROSA CLI section can now be found nested inside the CLI Tools heading. For more information, see xref:../cli_reference/index.adoc[CLI tools overview].
309
321
@@ -315,6 +327,12 @@ For more information on region availabilities, see xref:../rosa_architecture/ros
315
327
* **ROSA CLI update.** The ROSA CLI (`rosa`) was updated to a new version. For information about what has changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.23[ROSA CLI release notes]. For more information about the ROSA CLI (`rosa`), see xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-about_rosa-getting-started-cli[About the ROSA CLI].
316
328
317
329
* **{product-title} region added.** {product-title} is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
330
+
ifdef::openshift-rosa-hcp[]
331
+
* **ROSA region added.** {product-title} (ROSA) is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
| xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-hcp-service-definition[{hcp-title} service definition]
0 commit comments