openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-9610 HCP node limit to 500 workers

Browse Source
This commit is contained in:
xJustin
2024-02-22 16:57:47 -05:00
committed by openshift-cherrypick-robot
parent 40d2ae708b
commit f810569436
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc
View File

@@ -24,7 +24,7 @@ include::modules/rosa-sdpolicy-am-aws-compute-types-graviton.adoc[leveloffset=+1
[NOTE]
====
Currently, {hcp-title} supports a maximum of 90 worker nodes.
Currently, {hcp-title} supports a maximum of 180 worker nodes.
====
[role="_additional-resources"]

2
rosa_release_notes/rosa-release-notes.adoc
View File

@@ -16,6 +16,8 @@ toc::[]
[id="rosa-q3-2024_{context}"]
=== Q3 2024
* **{hcp-title} cluster node limit update.** {hcp-title} clusters can now scale to 180 worker nodes. This is an increase from the previous limit of 90 nodes. For more information, see xref:../rosa_planning/rosa-limits-scalability.html[Limits and scalability].
* **IMDSv2 support in {hcp-title}.** You can now enforce the use of the IMDSv2 endpoint for default machine pool worker nodes on new {hcp-title} clusters and for new machine pools on existing clusters. For more information, see xref:../rosa_hcp/terraform/rosa-hcp-creating-a-cluster-quickly-terraform.adoc#rosa-hcp-creating-a-cluster-quickly-terraform[Creating a default ROSA cluster using Terraform].
* **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 ROSA with HCP clusters].